Sorry, I think my question wasn't clear enough. I was actually asking for the environment variable dependencies. I already found the place where the registry keys regarding VS are retrieved, but either the read routines for retrieving the registry keys depend on some environment variables or CMake is reading them itself which causes it to fail when running with empty environment. So let me rephrase the question like this: Are there hardcoded environment variable dependencies in CMake's source code that you are aware of or is all of the VS compiler identification logic implemented in the .cmake module files? In the latter case I could just work around my issue by patching these files. Otherwise I'd be out of luck. Mit freundlichen Grüßen / Best regards
Johannes Asal Entwicklungsingenieur Software | Identification & Measuring Research & Development SICK AG | Nimburger Str. 11 | 79276 Reute | Germany Phone +49 7641 469-1460 | Fax | mailto:[email protected] | http://www.sick.de SICK AG | Sitz: Waldkirch i. Br. | Handelsregister: Freiburg i. Br. HRB 280355 Vorstand: Dr. Robert Bauer (Vorsitzender) | Reinhard Bösl | Dr. Mats Gökstorp | Dr. Martin Krämer | Markus Vatter Aufsichtsrat: Gisela Sick (Ehrenvorsitzende) | Klaus M. Bukenberger (Vorsitzender)
-- 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
