Skip to Content

Changes for page Debugging WOLips

Last modified by Pascal Robert on 2012/02/11 05:22
From version 74.1
edited by mark_ritchie
on 2009/09/12 23:11
Change comment: There is no comment for this version
To version 66.1
edited by mark_ritchie
on 2009/09/14 02:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,6 +14,16 @@
14 14  * Java 1.5.0//19//
15 15  * Eclipse 3.4.2 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz)
16 16  
17 +{{panel title="Snow Leopard Update" bgColor="#FFFFCE"}}
18 +
19 +I gave this a go on Snow Leopard and it worked fine with one little detail which I've noted at the end of this page.
20 +Here's the setup I was using:
21 +- Mac OS X 10.6.1
22 +- Java 1.6.0_15
23 +- Eclipse 3.4.2 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz)
24 +
25 +{{/panel}}
26 +
17 17  == Checking out the source code ==
18 18  
19 19  **A note for the impatient - don't try to checkout the source right into Eclipse. The files aren't structured in a way that allows this to work. I know because I tried to do it that way first!** ;-)
... ... @@ -132,3 +132,26 @@
132 132  This will be a clean version of Eclipse with the workspace which you set and any other settings.
133 133  By default, all of the plugins are loaded and ready for testing!
134 134  And now, you should be running inside the debug version of Eclipse with all the wolips bits to play with!
145 +
146 +== Snow Leopard Update ==
147 +
148 +I was running the carbon version of Eclipse 3.4.2 on Snow Leopard.
149 +Up to this point, I was following the instructions above however when I tried to launch Eclipse, I got this error:
150 +
151 +{{code value="java"}}
152 +
153 +java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
154 + at org.eclipse.swt.internal.Library.loadLibrary(Library.java:177)
155 + at org.eclipse.swt.internal.Library.loadLibrary(Library.java:151)
156 + ...
157 +
158 +{{/code}}
159 +
160 +This is a known problem and is documented <a href="http:~/~/www.eclipse.org/swt/faq.php#cocoa32launch">here</a>
161 +The fix is to add the --d32 parameter to the launch arguments.--
162 +
163 +Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl}
164 +Updated: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl} --d32--
165 +
166 +My final setup looked like this:
167 +[[image:32Bit_jvm_arguments.png]]