On 02/25/2016 05:51 AM, Stuermer, Michael SP/HZA-ZSEP wrote: > The part that probably needs most additional work is all the > C# detection and configuration part in the module scripts.
In your branch Modules/CMakeDetermineCSharpCompiler.cmake currently has a lot of logic and environment checks for this. It shouldn't need to be that complicated. Anything requiring deep introspection of the system (especially the registry) should be something done in the C++ generator implementation and provided to CMake platform files as a variable. For example, the VS generators always provide msbuild: https://cmake.org/cmake/help/v3.5/variable/CMAKE_VS_MSBUILD_COMMAND.html For the path to the compiler tool, take a look at Modules/CompilerId/VS-10.vcxproj.in and use of it by Modules/CMakeDetermineCompilerId.cmake. That all runs while detecting the compiler id using a small test project. It has a custom command that searches the PATH in the IDE project build environment to print out the path to the compiler. You should create one like this for CSharp too. We'll also need to define behavior when CSharp is enabled by projects under a non-VS generator. Other generators should reject any such attempt with an error message. Thanks, -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
