Due to the change in the development environment, the original Juno 32-bit is replaced with the 64-bit Juno 64-bit SP1 environment. The following error is returned when eclipse is started:
"Failed to load the JNI shared library "E: \ 2000 \ Java \ jdk6 \ bin \ .. JRE \ bin \ Client \ JVM. dLl"
For other environments, the default JDK 1.6.0 _ 37 32-bit is used. The default value is set to java_home and the path is E: \ 2000 \ Java \ jdk6.
Therefore, JDK 1.6.0 _ 37 is newly installed with the path E: \ 2000 \ Java \ jdk64, and an error is reported again when eeclipse is started.
Think about it. When eclipse is started, it should first look for JVM from its own configuration, so add two lines in eclipse. ini:
-VM
E: \ 2000 \ Java \ jdk64 \ bin \ javaw.exe
Still error, same as above. Therefore, java_home is set to E: \ 2000 \ Java \ jdk64 in the system environment variable. This time it can be started normally, but the same error is reported when other systems use 32 bits. Check eclipse. ini carefully and findOpenfileThe following items are added:
-VM
E:/2000/Java/jdk64/bin/javaw.exe
I used to add it to the end of the file with an incorrect position, so it did not take effect. (Monthly invitation note:You can also put the original two rows in openfile.) ThenJava_home is reset to: e: \ 2000 \ Java \ jdk6
Try againE: \ 2000 \ Java \ eclipse \ eclipse.exe-clean-nl en_us restart eclipse, and an error is returned:JVM terminated. Exit code =-1
Take a closer look and consider the possible memory parameter issues:
Set:
-Vmargs
-Dosgi. requiredjavaversion = 1.5
-Dhelp. Lucene. tokenizer = Standard
-Xms40m
-Xmx512m
To:
-Vmargs
-Dosgi. requiredjavaversion = 1.5
-Dhelp. Lucene. tokenizer = Standard
-Xms40m
-Xmx256m
Restart.
After normal startup, change to 512 M,Eclipse can still be started normally. It seems that eclipse hasSmartRemember the correct configuration.