Changes for page Debugging WOLips
Last modified by Pascal Robert on 2012/02/11 05:22
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,14 +16,11 @@ 16 16 17 17 {{panel title="Snow Leopard Update" bgColor="#FFFFCE"}} 18 18 19 -I gave this a go on Snow Leopard and it worked okhowevertherewereafew problemswhich I'vedetailednearthe end of thisdocument.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 20 Here's the setup I was using: 21 -- Mac OS X 10.6. 221 +- Mac OS X 10.6.1 22 22 - Java 1.6.0_15 23 -- Eclipse 3.4.2 Build id: M20090211-1700 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz) 24 -- woproject svn repository version 6031 25 -- Wonder svn repository version 10655 26 -YMMV! 23 +- Eclipse 3.4.2 (eclipse-SDK-3.4.2-macosx-carbon.tar.gz) 27 27 28 28 {{/panel}} 29 29 ... ... @@ -124,9 +124,9 @@ 124 124 When building woenvironment, you might hit this error: 125 125 Cannot find artifact for parent POM: org.objectstyle.woproject:woproject-all-parent::2.1 for project org.objectstyle.woproject.ant:woenvironment:jar:2.1-SNAPSHOT at /Users/... 126 126 127 -The simple solution is delete the pom.xml file. Full details are h ere: [[http://wiki.objectstyle.org/confluence/display/WOL/mail/6259075]]124 +The simple solution is delete the pom.xml file. Full details are <a href="http:~/~/wiki.objectstyle.org/confluence/display/WOL/mail/6259075">here</a> 128 128 129 -== The configuration setup == 126 +== The run configuration setup == 130 130 131 131 At this point, you should have a long list of packages which should all be compiling. 132 132 If that's not the case, please document additional steps here, making special note of your setup. ... ... @@ -155,7 +155,7 @@ 155 155 156 156 == Snow Leopard Update == 157 157 158 -I was running the carbon version of Eclipse 3.4.2 Build id: M20090211-1700on Snow Leopard10.6.2155 +I was running the carbon version of Eclipse 3.4.2 on Snow Leopard. 159 159 Up to this point, I was following the instructions above however when I tried to launch Eclipse, I got this error: 160 160 161 161 {{code value="java"}} ... ... @@ -167,14 +167,11 @@ 167 167 168 168 {{/code}} 169 169 170 -This is a known problem and is documented h ere: [[http://www.eclipse.org/swt/faq.php#cocoa32launch]]167 +This is a known problem and is documented <a href="http:~/~/www.eclipse.org/swt/faq.php#cocoa32launch">here</a> 171 171 The fix is to add the --d32 parameter to the launch arguments.-- 172 172 173 173 Original: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl} 174 174 Updated: --os $target.os} --ws $target.ws} --arch $target.arch} --nl $target.nl} --d32-- 175 175 176 -A second problem which I encountered was running out of memory while running test version of Eclipse! 177 -I had to add the VM argument "-Xmx2G" and then 'Run' as opposed to 'Debug' the app. For the most part, that worked. 178 - 179 179 My final setup looked like this: 180 -[[image:32Bit_jvm_ 2GB_mem.png]]174 +[[image:32Bit_jvm_arguments.png]]