no swt-win32-3062

[bandi]

Hi! I would find it fine but my firse application wouldn's run!
the problem is the following: :evil:

java.lang.UnsatisfiedLinkError: no swt-win32-3062 :?: in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:100)
at org.eclipse.swt.internal.win32.OS.<clinit>(OS.java:18)
at org.eclipse.swt.graphics.Device.init(Device.java:564)
at org.eclipse.swt.widgets.Display.init(Display.java:1780)
at org.eclipse.swt.graphics.Device.<init>(Device.java:100)
at org.eclipse.swt.widgets.Display.<init>(Display.java:355)
at org.eclipse.swt.widgets.Display.<init>(Display.java:351)
at org.eclipse.swt.widgets.Display.getDefault(Display.java:993)
at Bandi.main(Bandi.java:30)
Exception in thread "main"

what may the problem be? where should I set this library?

pls mail it to me if possibe!
bandi AT c2 DOT hu
thanx:
Bandi

[Eric Clayberg]

java.lang.UnsatisfiedLinkError: no swt-win32-3062 in java.library.path

You need to add the Eclipse SWT DLL to your path.

[mdfst13]

In my case, I also had to extract the DLLs from their jar file. If you don't already have something installed, I have been told that WinZip is capable of extracting the DLLs from the jar file. After I had extracted the DLLs, I was able to point at it using the instructions from 4.2.1.3 "Running the Example" on page 161 of the 1st edition. Note that your path may be (in fact, probably should be) different from that shown. I used "double quotes" around the path to make up for the space in "Program Files".

Hth,
Matt

[Eric Clayberg]

In my case, I also had to extract the DLLs from their jar file. If you don't already have something installed, I have been told that WinZip is capable of extracting the DLLs from the jar file. After I had extracted the DLLs, I was able to point at it using the instructions from 4.2.1.3 "Running the Example" on page 161 of the 1st edition. Note that your path may be (in fact, probably should be) different from that shown. I used "double quotes" around the path to make up for the space in "Program Files".

Note that this section has been updated in the Second Edition of the book to recommend using an SWT Application Launch Configuration (Run As > SWT Application) rather than a Java Application Launch Configuration (Run As > Java Application). Using an SWT launch configuration eliminates the need for extracting the SWT DLL from the SWT JAR file.

Extracting the SWT DLL from the SWT JAR was never necessary under Eclipse 3.0 as the DLL was provided as a file within the Eclipse SWT plugin directory. Eclipse 3.1 introduced the notion of JAR'ed plugins and the further need to extract the DLL from the JAR.