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 as far as CMake script is concerned.
Also I think we're using the android glue stuff in our existing project, but I'm not really sure what android glue is or if it is relevant to the CMake setup. On Tue, May 6, 2014 at 2:45 PM, J Decker <d3c...@gmail.com> wrote: > 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 <debug/release' step... there is a > step before that I do that is 'android.bat update project --target > "android-14" --path' which makes a few other files from the build.xml. > > > On Tue, May 6, 2014 at 8:42 AM, Robert Dailey <rcdailey.li...@gmail.com> > wrote: >> >> 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 there's some reference material out >> there but I'm not sure what to pay attention to. Would be nice to get >> some overview steps that I can read along with the reference material >> so I know the order in which to look at things, essentially. >> >> On Tue, May 6, 2014 at 10:32 AM, Bill Hoffman <bill.hoff...@kitware.com> >> wrote: >> > 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 >> > information on each offering, please visit: >> > >> > CMake Support: http://cmake.org/cmake/help/support.html >> > CMake Consulting: http://cmake.org/cmake/help/consulting.html >> > CMake Training Courses: http://cmake.org/cmake/help/training.html >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Follow this link to subscribe/unsubscribe: >> > http://www.cmake.org/mailman/listinfo/cmake >> -- >> >> 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 >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> http://www.cmake.org/mailman/listinfo/cmake > > -- 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 information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
