On 04/28/2014 01:07 PM, Brad King wrote: > It looks like in this case users will have to tell Xcode what tool > to use up front using the CMake generator toolset feature (cmake -T). > I think this is acceptable because it only affects old Xcode versions. > Otherwise we will need a much more complicated compiler id bootstrap > process
Actually it is not so complicated because the determination of the sysroot and deployment target does not depend on the language. I just had to introduce a platform-specific initialization step after the system is determined but before the compilers are: Add platform-specific initialization step when enabling languages http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=416761e3 OS X: Factor a Darwin-Initialize module out of Platform/Darwin http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0200d0a9 Xcode: Use sysroot and deployment target to identify compiler http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0cce556b Now the Xcode compiler identification finds the right one. I've reverted my change to the machine-specific dashboard script. -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
