yes basically
INSTALL( PROGRAMS ) keeps file permissions instead of INSTALL( FILES
... ) which loses file permisisons
You don't nessiciarly have to run it by hand, can add a target that could
be built...
There is a little more work associated with release APK
---
if( CMAKE
So basically I am thinking of doing this:
1. Build my NDK libraries using the android cmake toolchain file as if
I'm just building normal C++ libraries on Linux with the CMake
provided makefiles in the binary output directory.
2. Create a Java project using the 'android create project' tool and
ch
How do I tell my android Java project where the *.so files are so it
can package them into the APK for dynamic loading when I call
System.loadlibrary() on the SO files?
On Tue, May 6, 2014 at 6:59 PM, Eric Wing wrote:
> So I have 4 examples I actually tried to document.
> These all use my fork/de
So I have 4 examples I actually tried to document.
These all use my fork/derivative of the Android-CMake toolchain, which
I believe comes from OpenCV. (It had grown stale with later NDKs and I
hit problems). All of these rely heavily on the external NDK module
system (NDK_MODULE_PATH).
The first a
This is a page on building to android; mostly it's about my library, but
names can be replaced where required
https://code.google.com/p/c-system-abstraction-component-gui/wiki/BuildingForAndroid
I went wit the separate cmake projects because I end up with multiple
android projects from the same li
'after copying to the correct location'
in mine the sources are 'installed' and then when I start the android
packaging, it first updates local copies in lib/armeabi/ and assets
openCV project produces a lot of target architectures in /lib/...
so really I have my normal project which builds
Well to be clear, the NDK libraries are compiled in eclipse after I
generate eclipse makefiles in CMake. Ideally, I want the CMake script
to also configure "ant" execution so that it builds java and links in
the NDK libraries. You say "just use the libraries", but I'm not sure
what this looks like
If you've built the sources into libs, you can just use the lib; my sources
are much too complex of a tree for ndk to support to build as sources..
The java sources are compiled at the 'ant wrote:
> There is also the question of how to handle the NDK sources and
> integrate them into the eclipse
There is also the question of how to handle the NDK sources and
integrate them into the eclipse workspace. For example, I believe NDK
sources must be under the 'jni' directory, but they won't be
structured that way in the source tree. So I'm not sure if the jni
directory is required. I realize ther
You can look at what we did for VES:
http://www.kitware.com/blog/home/post/642
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
inform
Hi Robert,
If you want, check out the excellent "android-cmake" project for some tips.
It covers a lot of different scenarios for Android:
https://code.google.com/p/android-cmake/
I put together a simple function to generate an APK from CMake:
https://github.com/arpg/rpg-cmake/blob/master/def_apk
once you have your libraries and java souces... need to put them in an
arrangement like the ndk-build script expects (in libs, src, res) and have
a build.xml and a androidManifest.xml
then just call
ant
this does the packaging, and results in a bin/-.apk
the next useful commands are
adb install
Hello,
I have been working on getting CMake working for Android projects. So
far, I have a custom toolchain file to build NDK libraries. I am also
able to generate makefiles for Eclipse, import those projects into
eclipse, and build from eclipse. All seems to be working fine from
that aspect.
The
13 matches
Mail list logo
