it creates libs/armeabi-v7a/libplasma.so (15 KB) but also obj/local/armeabi-v7a/libplasma.so (63 KB). I am curious why NDK produces two *.so files with very different sizes for each ABI, e.g. See here about configuring Eclipse to build the native code automatically. See here about choosing which emulator is used. Right-click your project and choose "Refresh", otherwise Eclipse might fail to upload the native code when it starts the emulator.įinally, to run the sample, right-click the project and choose Run As | Android application. "Compile thumb : plasma libs/armeabi-v7a/libplasma.so "Compile thumb : plasma libs/armeabi/libplasma.so After you build the native code on the command line, e.g.: C:\.\android-ndk-r7b\samples\bitmap-plasma>.\.\ndk-build That's in addition to the output folders created by ndk-build (obj and libs).Įclipse won't build the native code by itself, but it will automatically deploy the native code (e.g. project, project.properties) and folders (bin, gen, assets) alongside the existing code. Eclipse will create numerous extra files (e.g.classpath. Leave "Create Activity" and "Create a Test Project" unchecked. ndk-build Android NDK: Could not find platform files (headers and libraries) Android NDK: Please run build/tools/. However, the project will run fine if you do not change this field. when I am Trying to compile native C code like this: :/1. Click next and consider changing the "Package Name" field which defaults to "".in the bitmap-plasma sample, target=android-9 but. I also don't know why the two may be different (e.g. I don't know why Eclipse does not simply get this information from in AndroidManifest.xml or from the "target" line in default.properties. Eclipse does not seem to allow this to be changed later, at least not from the GUI.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |