But the cleanest solution for me was to KEEP 1.5 as the default. When I installed 1.6, I had messed around with /System/Library/Frameworks/amework/Versions, trying to get 1.6 to run as the system default. JavaVM FATAL: Failed to load the jvm library. _NSJVMLoadLibrary: NSAddLibrary failed for /System/Library/Frameworks/amework/Versions/CurrentJDK/Libraries/libjvm.dylib 10:53:55.443 eclipse Cannot find executable for CFBundle 0x116030 (not loaded) If you run Eclipse from a shell, you might see this: Exit code=-1” and a list of run-time options. The error I got was a mysterious “JVM Terminated. There’s a great blog post, “Running Eclipse on MacBooks with Java 6”, written by one “rkischuk,” that explains why: 1.6 doesn’t support 32-bit SWT-Cocoa bindings, so Eclipse will bomb. (You still can’t get 1.6 for 10.5.1, sadly.) I’ve been fiddling with 1.6 and Eclipse, trying to get them to play well together, and here’s what I’ve found so far.Įclipse itself needs to run on 1.5. Last week, Java 1.6 went out of Developer Preview and became an “official” release for Mac OS 10.5.2.
0 Comments
Leave a Reply. |