libs/armeabi/libcom_googlecode_android_scripting_Exec.so read problem

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run Eclipse
2. go to File->Import,

What do you see instead?
Archive for required library: 
'libs/armeabi/libcom_googlecode_android_scripting_Exec.so' in project 
'PythonAPK' cannot be read or is not a valid ZIP file

What version of the product are you using? On what operating system?
Win7

Original issue reported on code.google.com by mike...@gmail.com on 25 May 2012 at 11:13

[GoogleCodeExporter]

Have you tried re-extracting 
libs/armeabi/libcom_googlecode_android_scripting_Exec.so from 
script_for_android_template.zip, then refresh and clean the project in Eclipse?

I had this same exact issue with PerlAPK and that is how I solved it.

Original comment by brettway...@gmail.com on 1 Jun 2012 at 1:07

[GoogleCodeExporter]

I solved the problem by remove it from the buildpath:
libcom_googlecode_android_scripting_Exec.so 

Original comment by mike...@gmail.com on 1 Jun 2012 at 1:18

[GoogleCodeExporter]

Looks an Eclipse(>= 3.7?) bug, try this: Java Compler->Building->Build path 
problems - set Incomplete build path: to Warning

Original comment by anthony....@gmail.com on 1 Jun 2012 at 5:51

[GoogleCodeExporter]

To solve this, don't remove the 'libcom_googlecode_android_scripting_Exec.so ' 
from the build, it's needed. If you did remove it, then copy it back into your 
workspace: 'PythonAPK\libs\armeabi' and run 'Project->Clean', right click on 
the PythonAPK project and select 'Close Project', and then double click to open 
it again. Check that it shows up in the Package Explorer window under 
'PythonAPK\libs\armeabi'. Alternatively, you can just delete the project and 
import it back in again.

Next, as Anthony wrote, right click on the project and select 'Build 
Path->Configure Build Path', then under 'Java Compiler->Building' make sure 
'Enable Project Specific Settings' is checked. Under 'Build Path Problems' 
uncheck 'Abort build when build path errors occur' or change 'Incomplete build 
path' from Error to Warning. Click Apply and OK. 

The red 'X' icon appearing on the project in the Project Explorer window should 
change to a yellow '!' icon for warning instead of error. If it didn't, close 
and reopen the project (or restart Eclipse). On Windows, if you have a 
thumbnail file inside a build directory, you'll see a red X over that directory 
which will also prevent the build from occurring - just right click and delete 
the thumbnail file.

Original comment by danielop...@gmail.com on 1 Jun 2012 at 4:34

• Changed state: Done

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Since this seems to be a bug with Eclipse, this issue is considered "Done", 
however, I will leave the status set to "New" so that it's more easily visible. 
I'll also add this info to the Wiki tutorial.

Original comment by danielop...@gmail.com on 1 Jun 2012 at 4:39

• Changed state: New

[GoogleCodeExporter]

Same problem without sloved. I'm using Eclipse IDE for Java Developers, Vession 
1.4.2

Original comment by pik...@gmail.com on 13 Jun 2012 at 2:17

[GoogleCodeExporter]

I can confirm this is an Eclipse bug, following instructions above would cure.

Original comment by anthony....@gmail.com on 13 Jun 2012 at 11:24

[GoogleCodeExporter]

I had the same problem. For me, unchecking 'Abort build when build path errors 
occur' didn't work. Changing 'Incomplete build path' from Error to Warning 
worked. Can launch the app now.

Original comment by rvijayra...@gmail.com on 13 Jun 2012 at 6:37