Andreas Pakulat wrote: > On 19.04.09 13:31:22, Piotr Dobrogost wrote:
>> I get it. But wouldn't it be a GOOD THING to incorporate logic of >> vcvarsall.bat into cmake's module looking for VC? > That would mean it needs to find that file as first thing, because that > file actually uses its own absolute path to set the variables properly. And > at that moment you again have a problem when people have multiple VS > installations on the same machine. I guess multiple installations of VS is a very rare case. Wouldn't reading VS variables in registry help? Below is an example of how people try to manage this. Mattias Helsing wrote: > I have a vague memory of a similar problem. As I remember - I was > better off using %VS90COMNTOOLS%vsvars32.bat to source in the build > environment. Could you try this? -- Piotr Dobrogost *** curlpp.org - c++ wrapper for libcurl *** _______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake
