-d32 switch breaks export to app

[GoogleCodeExporter]

What steps will reproduce the problem?
1. add -d32 to VM arguments in a Run/Debug config
2. export to application
3. run application

What is the expected output? What do you see instead?
expected: application runs successfully.
actual: application fails to run; console shows ClassNotFoundException for
PApplet.

What version of the product are you using? On what operating system?
JRE 1.5, Processing 1.05, Eclipse 3.4.1, OSX 10.6.2

Please provide any additional information below.
the -d32 VM argument tells JVM to run in 32-bit mode instead of 64-bit, as
Processing has trouble with 64-bit mode, which is the default on OSX 10.6+.
 this is important for testing from Eclipse, but seems not to matter in a .app.

Original issue reported on code.google.com by ericsoco...@gmail.com on 1 Mar 2010 at 6:56

[GoogleCodeExporter]

This is the issue Eric is mentioning:

http://processing.org/discourse/yabb2/YaBB.pl?num=1251771520/0#12

Original comment by maddpar...@gmail.com on 1 Mar 2010 at 9:02

[GoogleCodeExporter]

Not sure about this one. The exporter simply passes all arguments from the 
run-configuration to the generated 
applet or application. If one doesn't want that switch for apps, they can 
eliminate it from the application's run 
configuration and leave it in the one for the applet. 

Original comment by daniel.c.howe@gmail.com on 2 Mar 2010 at 11:40

• Changed state: Started
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This should be fixed now.

Original comment by maddpar...@gmail.com on 17 Aug 2011 at 9:52

• Changed state: Fixed