[EMAIL PROTECTED] wrote:
the only way right now would be to wrap the nant invocation in a batch file that sets the environment variable before calling nant.-----Original Message----- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: 19. november 2004 20:27 To: Høst, Einar; [EMAIL PROTECTED] Subject: RE: [Nant-users] Choosing c++ compiler
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: vrijdag 19 november 2004 15:37
To: [EMAIL PROTECTED]
Subject: [Nant-users] Choosing c++ compiler
Hi,
I'm trying to compile a managed c++ assembly using my NAnt script on a co-worker's computer. He normally programs in VC++ 6, but he has installed the .NET SDK 1.1 as well. Now the problem is that the NAnt script invokes v12 of the c++ compiler instead of v13 as it should. I don't want to mess with his path environment variable, so I'm wondering if there is any way of telling NAnt where to find the right c++ compiler?
Nope, not right now.
Gert
As a workaround, is there any way of manipulating the path environment variable for the duration of the NAnt script?
Going forward it might be nice to be able to:
- have a <setenv> task that would allow you to set env vars for the current run - and for any externally spawned processes
- and/or set the environment on individual tasks ( assuming that they derive from ExternalProgramBase ) -- ie they spawn external processes.
Ian
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
