On 08/05/2013 03:45 PM, Brad King wrote: > One of the main purposes of the compiler <id> is to load platform > modules like "Platform/<os>-<id>-<lang>" and "Compiler/<id>-<lang>". > Most of the information in these files will be identical across > the upstream and vendor-specific Clang distributions so having a > separate compiler id may lead to confusion and duplication. > > Another approach is to introduce a CMAKE_<LANG>_COMPILER_VENDOR > variable to name the vendor (or _VARIANT?).
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. -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
