If you have

aapt: /lib/libz.so.1: no version information available

you need to :

1) Create a new Workspace in Eclipse.

2) Create a new Android Project

3) A few files at a time copy your old project's file (or manually merge Manifest.xml for instance), and solve issues.


The problem (for me at least !) was in :
- Eclipse Workspace

Of course, I had some errors in my Android project, but it shouldn't have broken Eclipse !


Both Workspaces have the lastest (10.1) plugin, but the new project has an additionnal file : proguard.cfg

What is libz?

And what is the file libz.so.1? Is it needed? If not find it and delete it

I 'may' have founded something...

Of course, browsing the web, I've founded information about recompiling libz, making links (ln), checking my xml files, changed Eclipse version (it seems the latest version doen't work well with latest KDE !), etc... nothing worked.

Yesterday, I have created a new empty workspace in Eclipse. Created empty Android app, and I didn't have the libz error

Maybe my previous workspace (used for 2 years) has an issue... I will have to copy all my codes/files a few files at a time between my old and new project..

I will have more information tonight. So, maybe there's an Eclipse issue here...

The cause may be that your libz is outdated. Had the same problem, downloaded 1.2.7 source http://www.zlib.net/, recompilted, installed to /usr/local/lib, and removed the symbolic link
rm /usr/lib/libz.so.1

eclipse and aapt is happy now.