Brad, the alias idea is great. They're sorta like macros, right? Another really simple example might be creating two different aliases to csc with different optimization arguments.
What if instead of putting the aliases in a separate config only file, there was an alias task that let you define aliases even in your own .build file. The "config" file could then just be a .build file that gets included by default in each "normal" .build file. Jason ----- Original Message ----- From: "Brad Wilson" <[EMAIL PROTECTED]> To: "NAnt Developers" <[EMAIL PROTECTED]> Sent: Friday, April 12, 2002 6:22 PM Subject: Re: [nant-dev] RE: FileSet question > Kevin Dente wrote: > > > I was worried about that same issue of compiler paths for cl - it would be > > great if it didn't need to be in the path, and would be even better if we > > could support multiple compiler versions. But would the config file > > solution force us to set one compiler version for the entire build? > > You could use "aliases" in the config file rather than just parameters. This > gives you the possibility of having multiple compilers: > > <config> > <aliases> > <alias name="csc" task="csc"> > <property name="compiler" value="c:\rotor\bin\csc.exe"/> > </alias> > <alias name="mcs" task="csc"> > <property name="compiler" value="c:\dev\mono\bin\msc.exe"/> > </alias> > </tasks> > </config> > > To further the re-use, you could have "x.build" look for "x.build.config" by > default. You could override this behavior by adding a new property to the > root element of a .build file which specifies which .config file you want to > use. That gets you the best of both worlds and allows you to re-use config > files to boot. > > Thoughts? > > Brad > > -- > Read my web log at http://www.quality.nu/dotnetguy/ > > > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
