On 08/08/2017 08:08 AM, Raffi Enficiaud wrote:
> I have looked a bit to the Android toolchains, and I have to say I found
> those quite complicated as a first reading :)
This note may help:
I don't think iOS will need all the toolchain and stl selection logic.
Ideally CMake would gain iOS platform modules such that one could
set CMAKE_SYSTEM_NAME to `iOS`.
> CACHE string "iOS find search path root")
> where this path is hard coded, and points to the fat static libraries
> prefix path of boost. If I remove this path, FindBoost does not find the
> boost libraries anymore (of course I am passing BOOST_ROOT). In
> addition, I have this:
> set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY)
> set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
> set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
These last three lines tell the find commands to only look at
paths re-rooted under CMAKE_FIND_ROOT_PATH and CMAKE_SYSROOT.
If boost is not under one of those then it won't be found.
> set(CMAKE_MACOSX_BUNDLE YES)
Is it possible to build any binary of any form on iOS without this?
If not then the iOS platform modules should set something to tell
the generators that this should always be enabled.
> set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED "NO")
Similarly for this, but perhaps only during `try_compile`.
I'm not familiar enough with iOS development to answer the rest of
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
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
Follow this link to subscribe/unsubscribe: