New Eclipse project files created and submitted

Hi guys,

I've finally got JOGL building in Eclipse properly on Windows and Linux. I submitted the project files as two pull requests, https://github.com/sgothel/gluegen/pull/3 and https://github.com/sgothel/jogl/pull/18.

This setup lets you use the Eclipse debugger, profiler, code navigation, et cetera. You can also run the JOGL unit tests from inside Eclipse just by right-clicking a unit test .java file and selecting "Debug As > JUnit Test".

These Eclipse project files don't contain any absolute paths, but you do have to set up the JRE and Ant in Eclipse properly or it won't work right. Instructions are at https://jogamp.org/wiki/index.php/Building_JOGL_in_Eclipse.

Note that those instructions currently tell you how to create the Eclipse project files for yourself -- you can skip those parts after these pull requests are accepted, because the project files will come with the code.

Enjoy!

-w

Is there any native dependency in the project files?

The project files I submitted (.classpath, .project, and .externalToolBuilders) have no dependency on anything outside the gluegen and jogl directories.

The user still has to set up their current JRE inside Eclipse, and they have to create an Ant user library inside Eclipse. But that's part of their personal Eclipse settings and doesn't go into the project files, it goes in the user's .metadata directory which is one level above the gluegen and jogl directories. That's also where things like the user's editor settings are stored.

It took quite a while to figure out how to make this work properly

Hi Wade,

I just went through your Building_JOGL_in_Eclipse article and it all worked perfectly.
Thanks a lot!

Hi Carlo! Nice to see you here  I'm glad that article worked for you -- just let me know if any parts were unclear.

You might be interested in the discussion at http://forum.jogamp.org/Re-Native-SWT-Binding-Test-td2600231.html. This is the rough beginning of an SWT GLCanvas that's part of JOGL 2, which would allow us to get multisampling on Windows without having to get SWT to accept the patch that you and I have been working on.

On 3/8/2011 9:30 PM, Wade Walker [via jogamp] wrote:
It was all very clear. Some things I noted during the process:
- I don't see how to reach Building_JOGL_on_the_command_line and
Building_JOGL_in_Eclipse from the main wiki page. Maybe
http://jogamp.org/jogl/doc/HowToBuild.html should be updated to point to
them?
- Building_JOGL_on_the_command_line implicitly assumes that one is using
a 32bit VM and 32bit MinGW (I had a 64bit jvm)
- in "Building_JOGL_in_Eclipse/Create an SWT user library" you may want
to add the steps to link swt's javadocs (they are in
eclipse/plugins/org.eclipse.platform.doc.isv_3.6.2.r362_v20110111.jar,
path within archive reference/api)

As to the SWT GLCanvas, that's extremely good news. I did investigate a
little further org.eclipse.swt, but the fix would be far from trivial
(implementing all the code for managing arb-extensions on multiple
platforms) and would duplicate funcionality already present (and
debugged) in jogl (or lwjgl).

Is there a bugzilla issue I can track to follow SWT-GLCanvas related
developments? Should I open one? ;-)

I created an enhancement request for the SWT GLCanvas at https://jogamp.org/bugzilla/show_bug.cgi?id=484.

Hi Wade,

I went through Building_JOGL_in_Eclipse again with Indigo. I was able to entirely skip the following steps:
- "Update Eclipse's Ant version": Indigo has a recent ant version
- "Create an Ant user library": don't know exactly how/why, but they seem to be in the classpath already

Ah, maybe the jars in jogl\make\lib\swt could be updated to version 3.7.

Also, following "Contributing_a_new_feature_or_fix" (btw many thanks to the author) I forked jogl to see if I can do something about bug 484. I'll have a closer look at it in the next days.

Cheers,
Carlo

Hi Carlo,

I created bug 507 (https://jogamp.org/bugzilla/show_bug.cgi?id=507) for this so it won't get forgotten. I'll upgrade this when I switch to Indigo (probably a week or so).

Thanks for reporting this!