[news.eclipse.platform.swt] Re: Java for Mac OS X 10.5 Update 1 (Java SE

["Grant Gayed" <grant_gayed@xxxxxxxxxx>]

This case of eclipse not running with a 64-bit JVM on OSX will not be fixed
for 3.4.  SWT needs to be ported to Cocoa first because Carbon is not
available in a 64-bit flavour.  This conversion to Cocoa should be planned
for 3.5 (I say "should be" only because the 3.5 plan does not exist yet).

Grant


"Stanislav Vodetskyi" <svo@xxxxxxxxxx> wrote in message
news:g13rsb$bhg$1@xxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Just wanted to note that we had this problem with developer preview
> versions of java6 for MacOS X. Obviously, eclipse itself also doesn't
> run when forced to use java6. I guess it would be nice to create an bug
> in bugzilla for this issue as it really is a blocker. Can we expect this
>   to be fixed in 3.4?
>
> Regards,
> Stanislav
>
> Simon Pope wrote:
> > Thanks. That makes a lot of sense. Bit of a bugger though. Better get
> > out the torches and pitchforks.
> >
> >
> >
> > Grant Gayed wrote:
> >> Hi Simon,
> >>
> >> From the grumblings happening on JavaLobby it sounds like this new JVM
> >> only
> >> comes compiled for 64-bits.  If that is the case then, though I'm not
> >> sure
> >> why this would affect the loading of swt's libraries, it probably
doesn't
> >> matter because swt's java code for OSX is written for 32-bit pointers
and
> >> therefore would not work with a 64-bit JVM anyways.  I don't think
> >> there's a
> >> way to make this work currently, other than reverting to the 1.5 JVM.
> >>
> >> Grant
> >>
> >>
> >> "Simon Pope" <skjpope@xxxxxxxxx> wrote in message
> >> news:fvc6u0$m83$1@xxxxxxxxxxxxxxxxxxxx
> >>> Hi,
> >>>
> >>> I'm running Eclipse 3.3.2 on OS X 10.5.2 (MacBook Pro, 64-bit Intel)
and
> >>>   I've just installed the latest JVM from Apple (Java SE 6 version
> >>> 1.6.0_05) that was included in the 04/29/08 Java Update from Apple.
> >>>
> >>> When running my application using the new JVM, it complains about an
> >>> UnsatisifedLinkError on the swt-carbon library (see details below),
but
> >>> running it under JVM 1.5 works just fine. What, if anything, is there
> >>> anything I can do to fix this? Is this a known problem, and if so,
> >>> what's the best way of addressing this?
> >>>
> >>> Thanks,
> >>>
> >>>
> >>> Simon Pope
> >>>
> >>> [Details of Exception ->
> >>>
> >>> java.lang.UnsatisfiedLinkError: no swt-carbon-3349 or swt-carbon in
> >>> swt.library.path, java.library.path or the jar file
> >>> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:219)
> >>> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:151)
> >>>
> >>> ... (the usual) ...
> >>>
> >>> at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
> >>> at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
> >>> ]
> >>
> >>