Lwjgl.jar Download

0 views
Skip to first unread message

Marthe Bernskoetter

unread,
Aug 5, 2024, 11:56:45 AM8/5/24
to onlalikalt
im a little stuck. I'm doing a little game in java, it's my first time, and i'm using sprites. I finally made it blink jaja, it's not much, but hey! I'm starting. the thing is that i'm using Netbeans 7.3 Ide, and my code runs. There's no problem. The problem comes when i export it as a jar. I export it and i get no error whatsoever, and the jar is created, but, i double click it, and nothing happens. Like, at all. Noting. I run it in Netbeans, and it runs. Any help would be really apretiated. Thanks in advice!

2) Alongside your jar, in whatever folder it is in, make a folder called 'lib'. Inside it, put all of the lwjgl jars that you are using. If you are using anything more than lwjgl.jar, lwjgl_util.jar, and jinput.jar, add it to the Class-Path variable in your MENIFEST.MF. Also, inside the lib folder, make a folder called 'natives' and take all of the native LWJGL files and put them inside that folder. That will be important for Step 3.


This is a "secret switch" used to enable the native files. It's smart, and only uses the natives for the operating system that the code is being run on, so don't worry about having all of the native files in the same directory.


So ive decided to start using LWJGL to test some stuff out. I have never used an api before and I do not know how to install it. could someone please run over how to install it, I already have the build noted in the engines section downloaded or is there another build I should use?


These are the two basics ones you will almost always need

8. Click the little arrow next to the lwjgl.jar and click Native library location

9. Navigate back to the LWJGL folder and go to native/your_os and hit ok


So I download and install the spine-libgdx source files project, but wait, there's a problem... needs the gdx-backend-lwjgl project source... so go get that, and wait.. not one, but two more projects needed.... this is getting ridiculous, so full-stop... come to this board and scour for more installation help, can't find it.


So now, after paying for a full license, and trying to follow various guides (not from esoteric per se that I can see), I use the LibGDX automated project from aurelion, and don't see how I'm supposed to incorporate the .jar file for Spine, simply and easily. Which is what I was expecting when I paid for Spine.


Nate, where is the simple, documented way to get up and running with incorporating JSON/binary files into our various build environments (for me, Windows Based Eclipse LibGDX, but I'm sure I'm not the only one looking for the documentation that gets us up and running).


Follow the libgdx instructions to configure your development environment for libgdx. Next, in Eclipse click File -> Import -> Existing projects and point it at the spine-libgdx folder you got from github (you can download a ZIP of the github repo from the github webpage, so you don't have to mess with git). Now in your Eclipse project properties -> Java Build Path -> Projects you just need to check that your project depends on spine-libgdx as well as the libgdx projects.


If you really want a JAR you can import the project into Eclipse as described above and click File -> Export -> JAR file. Or you can run scar on the spine-libgdx folder. Or you can use Ant or Maven if you prefer those tools. But you might as well run from source, it makes it easier for you to dig into it to see how it works as well as to stay up to date.


Note spine-libgdx depends on the gdx-backend-lwjgl project, which I see now is probably what is tripping you up. If you aren't running libgdx from source then you can edit the spine-libgdx project, remove the gdx-backend-lwjgl project dependency and have the project use the following libgdx JARs:


Note spine-libgdx only needs gdx-backend-lwjgl.jar and gdx-backend-lwjgl-natives.jar to run the examples in the "test" source directory. You can delete this directory and omit these LWJGL JARs if you like.


Third, the tutorial mentions some outdated code, which is why I went with the source. I see now that Spine builds the .skel file, and it now contains all of the animations within that SkeletonData file. Also, in looking thru, the draw function has been taken out from the SkeletonData, and is now its own SkeletonRenderer class. As I was able to follow along with the tutorial to at least get started, it wasn't too painful after getting the exclamation points to disappear in Eclipse.


Is there any way to still have animation files separate? (I'm thinking, updates as expansion packs, that include more animations, based on the same SkeletonData/Atlas, but as I see it now, need to send the entire SkeletonData)

3a8082e126
Reply all
Reply to author
Forward
0 new messages