![]() Note that the native JAR names are different for each platform, so you can use some or all of the native JARs together to create a multi-platform installation.įor a full desktop installation using native library files, here are the files you need. For a full desktop installation using native JARs, here are the files you need. Now you may copy the required JARs out of each jar folder and the native library files (if you're using them) out of each lib folder. An unzipped file has this general directory structure: Unzip all the downloaded files with 7zip. See JogAmp JAR File Handling, for details on native JAR files and custom JAR bundling. Only use the native library files directly if you need fine control over native library file placement or if your app doesn't have permissions to create temporary directories. Using native JARs is usually easiest, since there are fewer files to manage and it allows different platforms' native library files to coexist in the same directory. ![]() When using native library files, JOGL just loads them directly from where they sit, with no unzipping. When using native JARs, JOGL automatically unzips the native JARs at startup into a temporary directory, then loads the resulting. jnilib files (the "native library files" option). You can either download these native libraries wrapped up in JAR files (the "native JARs" option), or you can download them as separate. JOGL uses native libraries to interface with each platform's OpenGL library. You can check the test results on the build server to make sure you're not downloading a broken build. Note that these automatic builds may not have passed all the regression tests. Then download one of these files for each platform you're developing on:ģ2-bit Windows: jogl-2.0-bvvv-20yymmdd-windows-i586.7z 64-bit Windows: jogl-2.0-bvvv-20yymmdd-windows-amd64.7z 32/64-bit Mac OS X: jogl-2.0-bvvv-20yymmdd-macosx-universal.7z 32-bit Linux: jogl-2.0-bvvv-20yymmdd-linux-i586.7z 64-bit Linux: jogl-2.0-bvvv-20yymmdd-linux-amd64.7z 32-bit Solaris: jogl-2.0-bvvv-20yymmdd-solaris-i586.7z 64-bit Solaris: jogl-2.0-bvvv-20yymmdd-solaris-amd64.7z Then, go back to this page and click on the most recent jogl-b* directory. Then download one of these files for each platform you're developing on:ģ2-bit Windows: gluegen-2.0-bvvv-20yymmdd-windows-i586.7z 64-bit Windows: gluegen-2.0-bvvv-20yymmdd-windows-amd64.7z 32/64-bit Mac OS X: gluegen-2.0-bvvv-20yymmdd-macosx-universal.7z 32-bit Linux: gluegen-2.0-bvvv-20yymmdd-linux-i586.7z 64-bit Linux: gluegen-2.0-bvvv-20yymmdd-linux-amd64.7z 32-bit Solaris: gluegen-2.0-bvvv-20yymmdd-solaris-i586.7z 64-bit Solaris: gluegen-2.0-bvvv-20yymmdd-solaris-amd64.7z Then navigate further down to archive and download the file jogamp-all-platforms.7z.įor example, on 1 20:19 CET, the latest aggregated autobuild was:įor the latest automatic build, we have to download gluegen and jogl separately.įirst, go to this page and click on the most recent gluegen-b* directory. Which shall be the latest aggregated autobuild. Got to this page and navigate into the first folder, now you are set to start using JogAmp module in your project.ĭownloading the latest aggregated autobuild attach the java-source files to the non-native JAR files (IDE).add the non-native JAR files to your CLASSPATH (IDE, manual.While keeping the above directory structure as-is, you can go ahead and If anything doesn't work as predicted, please follow our bugreport guide. Now you can test the archive as described Jogamp-all-platforms.7z Using the 7z jogamp-all-platforms archiveĪfter inflating the file with 7zip, you will have the general directory structure: Go to this page and download the all-in-one 7z archive file: 3 Downloading the latest automatic build.2 Downloading the latest aggregated autobuild.1.1 Using the 7z jogamp-all-platforms archive.1 Downloading the latest stable version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |