J Decker wrote: > I think this is impractical... the native activituy doesn't provide a hood > to call 'main' and while you may have special code to treat main as an > export and dynamically load it, actually stubstitute the single program > with a loader dll and the program as a DLL, and the loader DLL has custom > code depending on the package. The reason to do this is to support a > package that support multiple entry points; the library and class name > must be different to have a separate launcher icon
Thanks for the feedback. I do need sanity checking here :). Your message seems to be concerned with use-cases mine was not concerned with though (such as multiple entry points). My proposal is concerned with writing cross-platform cmake code. So add_executable(myappname ...) instead of if (ANDROID) add_library(myappname ...) elif(...) ... else() add_executable(myappname) endif() In that scenario, I have an application (one entry point) which I want to build for multiple platforms. Thanks, Steve. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
