Failed to load the JNI shared library on starting Eclipse
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
and get $2,000 discount on your first invoice
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Puzzle Game 5 Looping
--
Chapters
00:00 Failed To Load The Jni Shared Library On Starting Eclipse
00:38 Accepted Answer Score 35
01:11 Answer 2 Score 1
01:53 Answer 3 Score 1
02:06 Answer 4 Score 3
02:24 Thank you
--
Full question
https://superuser.com/questions/186001/f...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#eclipse
#avk47
ACCEPTED ANSWER
Score 35
This usually happens if you have a 32- vs. 64-bit mismatch between the installed JDK and Eclipse versions!
Your version of Eclipse is trying to access a 32-bit JDK (as indicated by C:\Program Files (x86)), but either fails because Eclipse is expecting a 64-bit JDK or because the 32-bit JDK is missing - consequently you'll need to make sure to match the Eclipse and JDK versions bit wise accordingly.
ANSWER 2
Score 3
I had installed both JDK and Eclipse 64-bit versions, but had the same issue...
Finally I discovered that my %PATH%
system variable didn't include the folder. Don't forget to change it to the correct folder where your JDK\bin is installed. Worked for me.
ANSWER 3
Score 1
If you have downloaded 64-bit Eclipse and a 64-bit JDK/JRE, check the availablity of javaw.exe for 64-bit.
In my case it was in C:\Program Files\Java\jre6\bin
I have extracted Eclipse to the c:\eclipse
folder; within that the eclipse.ini
file is available. Replace the contents of that file with the following:
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
-framework
plugins\org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xmx700m
-XX:MaxPermSize=690M
Leave the new line in between the -vm flag and the value. It worked for me.
ANSWER 4
Score 1
I had a 64 bit Eclipse and 32 bit Java and had the same issue. After installing 64 bit Java and updating system path, no issues.