Downloading and installing JOGL: Difference between revisions
m (Removed a few apostrophes and changed a few word choices) |
No edit summary |
||
| Line 1: | Line 1: | ||
To manually install JOGL, all you have to do is download the platform ZIP archives, | To manually install JOGL, all you have to do is download the platform ZIP archives, | ||
containing JARs and native libraries for your platform, and extract them in the directory of your choice. No installer is necessary. | containing JARs and native libraries for your platform, and extract them in the directory of your choice. No installer is necessary. | ||
See [{{SERVER}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment]. | |||
You have a choice of versions to download. The latest stable version is probably safer, but lags behind in features. The latest automatic build contains all checked-in code, but may be failing some tests. | You have a choice of versions to download. The latest stable version is probably safer, but lags behind in features. The latest automatic build contains all checked-in code, but may be failing some tests. | ||
| Line 9: | Line 11: | ||
which describes the following locations to download the platform ZIP archives from: | which describes the following locations to download the platform ZIP archives from: | ||
* [ | * [{{SERVER}}/deployment/ Deployment Home] | ||
* [ | ** [{{SERVER}}/deployment/jogamp-current/archive/ Signed Release] | ||
* [ | ** [{{SERVER}}/deployment/jogamp-next/archive/ Signed Candidate] | ||
** [{{SERVER}}/deployment/jogamp-next/v2.0-rc3archive/ Specific Version] | |||
* | |||
You'll need to download your [[Jogamp_Versioning_and_Releases#Release_and_Archived_Files|platform's 7z archive]. | |||
You may also extract the API documentation: | You may also extract the API documentation: | ||
| Line 65: | Line 61: | ||
Now you may copy the required JARs out of each <tt>jar</tt> folder and the native libraries out of each <tt>lib</tt> folder. | Now you may copy the required JARs out of each <tt>jar</tt> folder and the native libraries out of each <tt>lib</tt> folder. | ||
This installation contains all of JOGL. If you want to trim it down, see | This installation contains all of JOGL. If you want to trim it down, see [{{SERVER}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information. | ||
Revision as of 15:02, 20 September 2011
To manually install JOGL, all you have to do is download the platform ZIP archives, containing JARs and native libraries for your platform, and extract them in the directory of your choice. No installer is necessary.
See [{{SERVER}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment].
You have a choice of versions to download. The latest stable version is probably safer, but lags behind in features. The latest automatic build contains all checked-in code, but may be failing some tests.
Downloading a released version
JogAmp follows a release scheme, which describes the following locations to download the platform ZIP archives from:
You'll need to download your [[Jogamp_Versioning_and_Releases#Release_and_Archived_Files|platform's 7z archive].
You may also extract the API documentation:
- gluegen-javadoc.zip
- jogl-javadoc.zip
- jocl-javadoc.zip
- joal-javadoc.zip
Downloading the latest automatic build
Every time changes to the JOGL code base are checked in, it starts an automatic build and test process. The resulting builds are placed at https://jogamp.org/deployment/autobuilds/master/, where you can download a build as one big file. Just pick the most recent jogl-b* directory, then download the right zip file for your platform from it. For 64-bit Windows the file will be jogl-2.0-bvvv-2010mmdd-windows-amd64.zip.
Note that these automatic builds may not have passed all the regression tests. You can check the build server at https://jogamp.org/chuck/ to see the test results for the automatic builds and make sure you're not downloading a broken build.
Unzipping the files
Unzip all downloaded platform ZIP archives (and the API doc's ZIP files) in a common folder. Using a common folder will leave the API documentation intact and resembles the original directory layout.
A common methodology is to unzip the platform ZIP archive and rename the new folder by its module name, for example:
unzip gluegen-2.0-b261-20110202-linux-amd64.zip mv gluegen-2.0-b261-20110202-linux-amd64 gluegen unzip jogl-2.0-b280-20110202-linux-amd64.zip mv jogl-2.0-b280-20110202-linux-amd64 jogl unzip gluegen-javadoc.zip unzip jogl-javadoc.zip
Now you have the following structure (the same for all modules):
gluegen/ gluegen/artifact.properties gluegen/javadoc/ gluegen/jar/ gluegen/lib/ gluegen/jnlp-files/ gluegen/LICENSE
Now you may copy the required JARs out of each jar folder and the native libraries out of each lib folder.
This installation contains all of JOGL. If you want to trim it down, see [{{SERVER}/jogl/doc/deployment/JOGL-DEPLOYMENT.html JOGL Deployment] for more information.