[Nant-users] Re: [nant-dev] multiple runtime support

2003-02-24 Thread Gert Driesen
Title: Message Ian,   But the config file won't let you discover the location and availability of runtimes.  You also need to be able to have the task behave differently within the same buildfile.  It's no use being able to define which framewokcompiler directory the csc task should use in a

[Nant-users] RE: [nant-dev] multiple runtime support

2003-02-24 Thread Ian MacLean
Title: Message I'm already looking at this problem by having settings stored in the config file. ie there would be a FrameworkCompilerDir and a FrameworkSDKDir paramater. These values will accessible from tasks and changeable from the build file. There will also be task specific settings so

[Nant-users] multiple runtime support

2003-02-24 Thread Gert Driesen
Hi,   I'm sorry for crossposting to both the users and developers list, but I think this is something that needs everyone's attention.   In my opinion we urgently need to come up with a strategy for implementing support for multiple runtimes, and for making tasks runtime-aware.  The release

Re: [Nant-users] missing source file does not break the build

2003-02-24 Thread Ian MacLean
Bruce, By default the fileset element only includes files that exist. That is to support wildcard matching. So if you had class1.cs wouldn't match either. However to get the result you're after use the asis attribute. so: will pass class1.cs thru to the compiler without

Re: [Nant-users] cl task and paths with white spaces

2003-02-24 Thread Ian MacLean
Derek, I hope this hasn't been asked a thousands times - I'm new to NAnt. No it hasn't otherwise it would have been fixed by now. This was a bug. Thanks for posting it. Everything else ( include dirs and such ) was quoted but not the source files. I've committed a fix for this in cvs. It updates

[Nant-users] cl task and paths with white spaces

2003-02-24 Thread Derek Puff
Hi, I hope this hasn't been asked a thousands times - I'm new to NAnt. I am attempting to use the "cl" task. The path in which my source files reside has white spaces in it. When NAnt turns the sources into arguments to cl, the arguments are not enclosed in quotes and cl barfs. Here's the targ

[Nant-users] General Usage Strategies

2003-02-24 Thread Nau, Michael
Hello, Can anyone provide some insight as to the best way to support both a VS.NET IDE and an nAnt build environment? Our developers need to use VS.NET to develop and test their components and I need some way to build and test the components in an automated environment. When setting up the nAnt

[Nant-users] missing source file does not break the build

2003-02-24 Thread Hearn, Bruce
when NANT contains a csc project with the following lines: ... If the file class1.cs file is not present on disk, no error message is generated. The project will compile with only class2.cs. The absence of class1 will only be noticed when another project that references

[Nant-users] [Fwd: Usage question...]

2003-02-24 Thread Tony Boggis
Hmmm, seems the mailing list strips '\' [Windoze directory/path slash] chars... so here's my question again. Hopefuly the slashes won't be stripped this time, since I replace them with '/'. Scenario: Base directory (location of .build file) is "E:/IAP Dev/Source". Under this are sub-pro

[Nant-users] Usage question...

2003-02-24 Thread Tony Boggis
Scenario: Base directory (location of .build file) is "E:IAP DevSource". Under this are sub-project directories: a, b, c etc... In SOME sub-projects are files matching the template '*.sq?'. I need to execute a task (exec) on each matching file found. Nexted loops almost do the trick, b