Databases
StackOverflow2013
Postsdbo
POJava .jar not running on windows
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava .jar not running on windows
    text
    copied!<p>I am developing using Eclipse under Fedora 15. I exported a runnable <em>jar</em>. It works fine in Fedora. But I can't run it on windows. I have installed a JRE. I even tried installing JDK. There are no error logs, app just didn't start.</p> <p>Here's the output</p> <pre><code>Microsoft Windows [Version 6.1.7601] (c) Корпорация Майкрософт (Microsoft Corp.), 2009. Все права защищены. C:\Users\Артоюрос&gt;java -jar C:\Lib.Ru2Epub.jar Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoa der.java:58) Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-gtk-3735 in java.library.path no swt-gtk in java.library.path Can't load library: C:\Users\└ЁЄю■Ёюё\.swt\lib\win32\x86\swt-gtk-3735.dl l Can't load library: C:\Users\└ЁЄю■Ёюё\.swt\lib\win32\x86\swt-gtk.dll at org.eclipse.swt.internal.Library.loadLibrary(Library.java:285) at org.eclipse.swt.internal.Library.loadLibrary(Library.java:194) at org.eclipse.swt.internal.C.&lt;clinit&gt;(C.java:21) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63) at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54) at org.eclipse.swt.widgets.Display.&lt;clinit&gt;(Display.java:132) at ru.lib.epub.MainWindow.main(MainWindow.java:28) ... 5 more C:\Users\Артоюрос&gt; </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload