Additional Files

The Jet3D build from this CVS requires additional files that are not on the CVS server.  

You will need DirectX 7, which you can get at http://www.microsoft.com/directx/.
You will need the Intel C/C++ Compiler.  An evaluation version is available at http://www.intel.com/.
You will need MASM.
Other files not in the CVS are the levels and art that shipped with the beta distribution of Jet3D.  You can get them directly from the original distribution or from the CVS project home page at http://jetpp.sourceforge.net/.

 

Compiler and Path Settings

Intel C/C++ Compiler

You can install this anywhere you like, but make sure you set the INTELC environment variable to the full executable path:
SET INTELC=C:\IntelC\bin\icl.exe

MASM

You can install this anywhere you like, but make sure you set the MASM environment variable to the full executable path:
SET MASM=C:\MASM\bin\ml.exe

Microsoft Visual C++

Make sure you don't have any include or library paths set under Tools/Options/Directories for Jet3D or DirectX.  Paths for the Jet3D SDK, DirectX, etc. are all set at the project level now.
Set an environment variable called MSVCDIR that points to your installation directory.  Long file names are not supported in this variable, so use the short names.  For example:
SET MSVCDIR=C:\Progra~1\Micros~1\VC98
Once the above steps have been taken, you can load the main workspace file /jet/project/jet/jet.dsw.  After you build the Jet3D project, it will copy the include and lib files to the /jet/include/jet and /jet/lib/jet directories.  These are the directories you'll want to use when accessing Jet3D for your own projects.  They're also the directories the editor (JEdit) and other engine dependent projects use when compiling.

DirectX7

You need to set two environment variables to where you installed DirectX7.  For example:
SET DIRECTX_INCLUDE=C:\Jet\Include\DirectX7
SET DIRECTX_LIB=C:\Jet\Lib\DirectX7

 

Known Issues

 
If you have run JEdit from the beta distribution you should remove the registry key HKEY_CURRENT_USER\Software\Eclipse from the registry or some assertions will fire (release version will crash). This is because the docking works differently in these two versions.
If you try to run JEdit straight from the /jet/bin/ directory, make sure you've copied the /GlobalMaterials, /Actors, and /Sounds directories for the levels you'll be loading, as well as light.bmp, select.bmp, and ambient.bmp.

 

Documentation Notes

Comments or suggestions concerning this documentation should be directed to one of the following people:

Anatoly Sennov

Aaron Oneal (Incarnadine)