you are correct. Right now NAnt will find csc in the framework directory or the runtime its running against. As you've noticed this is sub-optimal when you're working against multiple versions of the framework.
What has been vaguely proposed is to define certain global settings in the .config file. So if the config file contained FrameworkDir="path to 1.0 framework" then csc would be found relative to that path. I would also like the ability to override this setting from a given .build file so you can have a default and then have different build files targetting different frameworks.
do you always have to pass /nostdlib and /noconfig when using the compact framwork ? If so then a set of default args could be added to the config file also.
To answer your previous question I don't think its advisable to add this support to the upcoming release. This release is well past due time so now is not the time to be adding major changes.
In the meantime you could work around it by hacking cscTask.cs
change line 41 from
public class CscTask : MsftFXCompilerBase to
public class CscTask : CompilerBase
this will cause nant to use the first csc.exe in the search path. You can add the required args manually with the <arg> tag.
Ian
Hi,
We're currently porting log4net to the .NET Compact Framework. For the next release (1.2.0), we will be supporting .NET Framework 1.0, .NET Framework 1.1 and .NET Compact Framework 1.0, so we want to use nant for automating the build process.
We have to be able to built the log4net assembly for all three .NET runtimes, is this possible using nant right now ? Currently, I think nant will always use the version of the commandline tools for the runtime version nant is using (eg. if nant is using .NET Framework 1.1, then the 1.1 version of the C# compiler and the assembly linker will be used) or am I wrong ?
I've figured out that, in order to compile an assembly for the .NET Compact Framework, you have to specify both the /nostdlib and /noconfig commandline options for the C# compiler (and of course you have to specify the full path to .NET Compact Framework system assemblies).
Will support for building assemblies for multiple platforms be incorporated in nant ?
Thanks,
Gert Driesen
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
