<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
KSpam wrote:
<blockquote cite="mid200805221120.22356.keesling_spam@cox.net"
type="cite">
<pre wrap="">HS,
On Thursday 22 May 2008 02:05:33 Hendrik Sattler wrote:
</pre>
<blockquote type="cite">
<pre wrap="">KSpam schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">Using this add-in would require that I create a corresponding .slnenv
file for each .sln file generated by CMake. In my case, the contents of
the .slnenv files can be the same (I am just setting PATH).
What is the best way to accomplish generating a .slnenv file for each
generated .sln file?
It seems like this type of capability would greatly enhance the usability
of CMake for developers using Visual Studio. Would this add-in make
sense as an enhancement to CMake?
</pre>
</blockquote>
<pre wrap="">What can it do that CMake doesn't already do? Nothing from a first look.
</pre>
</blockquote>
<pre wrap=""><!---->
As far as I can tell, CMake does not currently do this. When setting
environment variables via $ENV{PATH}, these variables are only in effect
during the CMake configuration and build file generation. I need the
variables to be in effect for the loaded solution file (When I run an
executable from Visual Studio, I need PATH to be setup to find the required
dlls).
There would probably be a way to accomplish this in CMake if it is possible to
set registry entries from CMake. I see that CMake can get registry entries;
however, I do not see that there is a way to set registry entries.
Am I missing something? Is there a way to set registry entries from CMake?
</pre>
</blockquote>
<pre wrap="">Having CMake set the necessary registry entries would not help with
binary distributions of your product. I do not whether that is relevant
to you, but in general that would be a problem:
- Your clients may have the libraries installed in a different place
- They may have different versions
- They may lack the permissions to install libraries
Come to think of it:
They may lack the permissions to update the registry.
How does the tool you mention handle that sort of situations by the way?
(Mind you, I am not trying to be sceptical - it is just that I have
run into all manner such problems before and a simple solution
seems utopic)
Regards,
Arjen
</pre>
<br>
</body>
</html>