java.library.path fix for MacOS X (7145798) (original) (raw)
Michael Hall mik3hall at gmail.com
Sat Feb 18 09:01:15 PST 2012
- Previous message: java.library.path fix for MacOS X (7145798)
- Next message: java.library.path fix for MacOS X (7145798)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 18, 2012, at 10:42 AM, Mike Swingler wrote:
The bundle directory has not been changed to "JavaVM", only the Info.plist key for the dictionary that describes all the Java options. Nothing should be attempting to assemble an (app)/Contents/JavaVM directory.
After you asked Greg to change the plist key he posted a updated demo that now shows.... ls /Volumes/SwingSet2/SwingSet2.app/Contents Info.plist MacOS PlugIns JavaVM PkgInfo Resources
JavaVM. Something extra got picked up with the plist change maybe?
But after you mentioning that I did try just changing the directory manually to 'Java' but that doesn't seem to show launching at all and has this in console...
2/18/12 10:52:08 AM JavaAppLauncher[611] Could not enumerate Java directory contents.: ( 0 CoreFoundation 0x00007fff83904784 __exceptionPreprocess + 180 1 libobjc.A.dylib 0x00007fff82739f03 objc_exception_throw + 45 2 CoreFoundation 0x00007fff839045a7 +[NSException raise:format:arguments:] + 103 3 CoreFoundation 0x00007fff83904534 +[NSException raise:format:] + 148 4 JavaAppLauncher 0x00000001a4b17bd6 launch + 1078 5 JavaAppLauncher 0x00000001a4b17676 main + 102 6 JavaAppLauncher 0x00000001a4b17604 start + 52 )
- Previous message: java.library.path fix for MacOS X (7145798)
- Next message: java.library.path fix for MacOS X (7145798)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]