Building: compilers

[Smoke]

well the "official" makefile requires either vc6 or 7 and i dont have both of them, and don't plan on buying  

is there a way to do one of
-download a vc6 or 7 compiler
-build with another (free) compiler
-somthing even smarter

sorry but i  know not much about vc++ exactly  

[Javabear]

Well, the good folks at Mind2Machine have prepared a Win32 build and made it available in the downloads section of their OpenMind Java game engine Sourceforge project. While they were at it, they compiled the other JSR-134 projects, so the download includes JOGL, JOAL, Jinput and Jutils.

http://sourceforge.net/project/showfiles.php?group_id=72173

[Smoke]

i know that one but thanks anyway  
there's also a jogl build build in the filesharing section of the jogl project now.

but both builds dont work with the new jogl demos, because the demos depend on the utils package that was very recently moved inside the jogl package. (so both builds dont have it)

Games published by our own members! Check 'em out!

[gregorypierce]

The jogl stuff can be built using the free compilers available on Windows such as those in the cygwin environment. Simply download it and follow the instructions in the readme file.

[Smoke]

i tryed using the cygwin gcc compiler already by changing the call of "cl" to "gcc" in te makefile but that didn't quite work out. different parameters....

could you please publish a makefile wich uses gcc or give me some hints how to replace cl by gcc?

[abies]

Please download mingw32 and then compile .c files with following instructions (they are taken from my build.xml, so you need to change them to whatever format you use):

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15

<exec dir="${obj.dir}" executable="gcc.exe">       <arg value="-D_WINGDI_"/>       <arg value="-DBUILD_DLL"/>       <arg value="-I../${stub.includes.opengl}"/>       <arg value="-I${java.include.path}"/>       <arg value="-I${java.include.path.pd}"/>       <arg line=" -D_STRICT_ANSI -D_JNI_IMPLEMENTATION_ -c"/>       <arg line="${native.files}"/> </exec> <exec dir="${obj.dir}" executable="gcc.exe">      <arg line="-o jogl.dll"/>       <arg line="*.o"/>       <arg line="-shared -Wl,--kill-at -L${jdk.home}/lib -lopengl32 -lglu32 -ljawt -lgdi32"/> </exec>

In reality, after substitution, commands on my system looked like:

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16

'gcc.exe' '-D_WINGDI_' '-DBUILD_DLL' '-I../../make/stub_includes/opengl' '-IC:/java/jdk1.4.2/include' '-IC:/java/jdk1.4.2/include/win32' '-D_STRICT_ANSI' '-D_JNI_IMPLEMENTATION_' '-c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\GLUImpl_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\JAWTFactory_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\JAWT_DrawingSurface_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\JAWT_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\WGL_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\build\gensrc\native\jogl\WindowsGLImpl_JNI.c' 'C:\java\eclipse-cvs\workspace\jogl\src\native\jogl\JAWT_DrawingSurfaceInfo.c'

and for linking

1   2   3   4   5   6   7   8   9   10   11

'gcc.exe' '-o' 'jogl.dll' '*.o' '-shared' '-Wl,--kill-at' '-LC:/java/jdk1.4.2/lib' '-lopengl32' '-lglu32' '-ljawt' '-lgdi32'

I'll try to modify build.xml from rgrzywinski to make this stuff automagically. Until then, play with command line

[Jeff]

This is very cool Abies, thank you muchly  

I'm going to point Dan at your post and maybe we can get the MinGW build integrated in to the release soon

(We wanted gcc for release, we just didnt have the time before J1 to get it all together.)

CQ

[abies]

I have modified build file made by rgrzywinski so you can build native dll with mingw compiler. Cygwin is not needed anymore - only java, ant, antlr and mingw32.

http://nwn-j3d.sourceforge.net/jogl/jogl-ant.zip

Patch against original build.xml is available at
http://nwn-j3d.sourceforge.net/jogl/build-rg.diff

Please remember - all credits are due to rgrzywinski, I have only added mingw32 target.

Some links which might be useful:

• Ant - http://ant.apache.org/
  
• Antlr - http://antlr.org/
  
• Mingw32 - http://www.mingw.org/
  

[swpalmer]

(We wanted gcc for release, we just didnt have the time before J1 to get it all together.)

If we have precompiled binaries available lets be sure that they AREN'T compiled with GCC.  The code produced by GCC isn't nearly as good.  I know for tiny bindings like this it won't matter much, but just in principle... if you have access to a better compiler it makes sense to use it.

[abies]

If we have precompiled binaries available lets be sure that they AREN'T compiled with GCC.  The code produced by GCC isn't nearly as good.  I know for tiny bindings like this it won't matter much, but just in principle... if you have access to a better compiler it makes sense to use it.

Do you really think that gcc is really so bad at compiling method containing single branch with one call inside ? I know that gcc is not very good generally, neither is MS VC++ - but this is not a reason to not use them for such simple things. I will say even more - standarizing on 'weaker' compiler - mingw - is better, because everybody can download 5MB mingw, but not everybody can get VC++ to compile the lib. And I really don't think that there is any performance difference for jogl between these two.

When we will talk about heavy-computation inside native code, we can ask somebody with Intel compiler to make really fast binaries. But until then, I think that free and small compilers are best common ground.

Games published by our own members! Check 'em out!

[swpalmer]

- I said in this case it probably wouldn't matter much.  GCC has too little to screw up in this case.

- I was talking about the pre-compiled binaries that would be made available for download from java.net.. Therefore it has nothing to do with who can get VC++.  JOGL already is set up to build with it.

- I have no argument against making it build-able with all the free tools you can find.  I was just pointing out that if binaries are made available at java.net it makes sense to use the best compiler you have  to build those "release builds".