On 08/06/2013 09:19 AM, Brad King wrote: > On second thought adding yet another dimension to the compiler > identification is just more complexity. We can use a separate > compiler <id> for each variant and simply have the platform > information modules for each vendor include the upstream one.
I've resolved this with a new AppleClang compiler id: Clang: Add separate "AppleClang" compiler id http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ab658624 and a policy for compatibility with project code expecting the old id for the compiler: Add policy CMP0025 for Apple Clang compiler id compatibility http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa53ee57 -Brad -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
