I'm not exactly sure what you're driving at with the aliases.  What
refers to the alias name attribute?  Is it something in the .build file?

I don't like the config file being referred to in the .build file,
precisely because I want to store platform specific settings in the
config file.  I don't want to have to change the .build file in order to
change compilers or to build the same target under Windows or Mono.  I'd
rather it be a command line option which config file to load, and if
it's not present use a platform specific file (probably in the same
directory as nant itself.  I realize you're saying that the config file
would optionally be refered to in the .build file, and there would be
some default.  I'd rather the default be system wide, I think.  If you
did have .build file specific config files, I think we need some sort of
include mechanism to get some reuse.

This sounds kind of negative, but it's really not.  I like hearing
everyone's viewpoints, you've already pointed out a few things I hadn't
considered.

Eric.

> -----Original Message-----
> From: Brad Wilson [mailto:[EMAIL PROTECTED]] 
> Sent: Friday, April 12, 2002 9:23 PM
> To: NAnt Developers
> Subject: Re: [nant-dev] RE: FileSet question
> 
> 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

_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to