I downloaded the Android PDF Viewer source code and am trying to compile it in Eclipse. Instead of messing with Cygwin and recompiling the native C libraries, my friend said
As mentioned another Stack Overflow thread about this topic switching off "Automatically refresh Resources and Assets folder on build" and "Force error when external jars contain native libraries" under Window/Preferences/Android/Build helps. At least it helped in my case!
And don't forget to put the so-file in 'lib s/armeabi' to have it availible at runtime.
Hope this helped others, also if it was too late for Li_W.
See how they set things up in the sample project: http://code.google.com/p/apv/source/browse/#hg%2Fpdfview
This NDK tutorial may also be useful in terms of helping you figure out how things work with the NDK: http://mobile.tutsplus.com/tutorials/android/ndk-tutorial/
The basics are this:
The .so library files typically go in the project_root_dir/libs subfolder. Also, generally they are in further subfolders that describe their architecture (e.g. project_root_dir/libs/armeabi/libpdfview2.so).
To use the library in an activity you add a static library loader to the activity as shown below:
static
{
System.loadLibrary("pdfview2"); // Notice lack of lib prefix
}
You then define the native functions you are importing. You can recognize these functions thanks to the native keyword. Look in the file below to see what functions they import in the sample:
http://code.google.com/p/apv/source/browse/pdfview/src/cx/hell/android/pdfview/PDF.java?r=560343d2dad904c5c925b6cadf97b90430fd25f4
Here are some examples:
private native int parseBytes(byte[] bytes);
private native int parseFile(String fileName);
private native int parseFileDescriptor(FileDescriptor fd);