On 03/27/2014 11:09 PM, Eric Wing wrote:
> One other issue I would like to see fixed is that it is impossible to
> change some of the settings like architecture after the first
> generation. I find that this makes the CMake GUI interface completely
> useless to me and I always have to load up all my parameters up front
> on the command line.
On the first "Configure" in a new build tree the cmake-gui pops up
a dialog to select settings for the toolchain to use. That could
be taught to be sufficient for selecting such information prior
to the first configuration if it is not already.
> Though, one other consideration is maintainability. Android keeps
> changing version numbers and moving/breaking things.
The upstream Android NDK folks may be open to distributing files
that are CMake-aware with the NDK. Then one could have a toolchain
file that does include(${ANDROID_NDK_ROOT}/.../toolchains.cmake)
to get information without scanning or globbing. What kind of
info would NDK-provided files need to have to be most useful?
Or, perhaps the NDK could actually provide the toolchain files.
-Brad
--
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
