[EMAIL PROTECTED] schrieb am 11.01.2005 17:42:40: > The behavior exhibited is not unique to Ant--it's how shells work. If you > open a shell (start->run->cmd) you'll get a shell. If you set env > variables in that shell, they don't persist to another shell that you > might open. > So the <exec> task in Ant is executing in a shell. Once the <exec> task
> completes, that shell is closed. The next <exec> task gets a new shell, > and hence the env variables are gone. > I agree w/ Chris Erskine's suggestion to write a batch file which calls > vsvars32.bat followed by the VS build. > Nick, thanks for the clarification. Should have read the first reply better which stated that <exec> creates a new process. -- Gilbert Jeiziner
