That’s great to know, thanks! Is there any plan on having their toolchain in CMake directly at some point?
I’m afraid that even if they update their options to use the upstream support, they may not allow using those options directly and we’ll still have to support 2 toolchains. That’s especially true if you chose not to build with Gradle but a standalone CMake build (using upstream) and then don’t have access to their toolchain file. /Orphis > On 27 Sep 2016, at 13:51, Brad King <brad.k...@kitware.com> wrote: > > On 09/26/2016 05:50 PM, David Neto wrote: >>> I just don't want to have 2 toolchains to support, that would be really >>> terrible :( >> >> I work for Google but not in this area, and I don't know who is doing this >> support. >> I suspect this is just an accidental duplication of effort. > > I have been in contact with them. They are aware of what CMake 3.7 will have > and plan to port their toolchain files to take advantage of it. They can > simply > map their options to CMake's new equivalents. > > The two efforts were mostly orthogonal. CMake's side of the work makes > toolchain files much simpler, but does not actually provide any toolchain > files. > The NDK's side of the work provides toolchain files that are aware of exactly > what comes with the NDK. > > -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/mailman/listinfo/cmake-developers
