Considering HLSL is DirectX only, I don't think we need (yet) to add it as a first-class language. And also because of time constraints, I might just go and add the COMPILE_FLAGS into the custom logic. I will send a patch when I can. Thanks!
-----Original Message----- From: Brad King [mailto:brad.k...@kitware.com] Sent: Monday, January 26, 2015 1:08 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] Setting additional compile flags to .hlsl files? On 01/26/2015 01:04 PM, Robert Goulet wrote: > Do we really need to go down the road of making hlsl a 'first-class' > language to add support for additional compile flags? Right now the Visual Studio generator has custom logic for .hlsl sources, so the rest of CMake knows nothing about them and treats them like .txt files. So, one could either add more custom logic to the VS .hlsl support to honor COMPILE_FLAGS, or add the needed infrastructure for enable_language(HLSL). The latter approach is much more general. -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
