Question

I seem to have a 32bit vs. 64bit problem here. It should be simple to solve, but I’m hoping you can help me by pointing out the problem. I really want to avoid re-installing OSs, Eclipse, several plugins, JDKs and JREs over and over again to find a working solution. Many thanks in advance!

I build on a 64bit Thinkpad, in 64bit Windows 7.
I have built an Eclipse RCP application in Indigo (3.7.1.), 32-bit version.
The only “Javas” I have on this machine is a 1.6.29 32bit JRE, and a 1.6.29 32bit JDK. I’ve installed these (perhaps in false assumption) to be able to build for 32bit systems, and not screw things up by building on a 64bit machine.

Seems I was wrong: when I export the application (as Eclipse product) I get the dreaded Java exit code=13:

I am sure this is somehow to do with the combination of 32bit software on a 64bit system (if you can prove me wrong, even better!).

Does one of you know how I can set this up properly and still be able to build for win32?

Again, many thanks!

UPDATE

I have installed 64-bit Eclipse 3.7.1, and JRE 1.6_30 + JDK 1.6_30, both 64-bit versions. However, the error remains! I think this might either be a bug, or I’m doing something else wrong.

First of all, here is the error message:

For this build, I didn’t use the Delta Pack but instead added the RCP SDK Software Site to the target definition, choosing the option “include all environments” (or similar).

Also in the target definition, I set the target environment to win32 (OS and WS) and x86_64 (arch). Furthermore, I set the Environment to use the default JRE.

In the product configuration, I set the Execution Environment to JavaSE 1.6, and set the JRE to be packaged.

Also, here’s my eclipse.ini:
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502

Any ideas?

Answer 1

Seems this had nothing to do with 32-bit vs. 64-bit and everything with my lack of experience. The product configuration simply wasn’t set up correctly. I’ve bypassed this by creating a new one which uses the automatically created plugin run config from when you start the application via the “Launch an Eclipse application” link in Eclipse itself.

For those who come across a similar problem, here is how it can be done.

1. Launch the application via “Launch an Eclipse application“
2. Go to Run > Run Configurations… and memorize the name of the run configuration
3. Create a new Product Configuration, and choose “Use a launch configuration:” in the wizard. From the dropdown list, choose the run configuration you have memorized in step 2.
4. Give the new product configuration an ID, Version and Name, and add further info (e.g., in the Product Definition section) as needed.
5. Synchronize and Launch from within Eclipse to see if everything works fine.
6. Export and be happy.