--- Scott Hernandez <[EMAIL PROTECTED]> wrote: > Those are good questions. > > My goal would be to get things working well enough so that the mono team > feels confident is using NAnt to do their builds.
That at least may be an easier first goal. The MCS task and possibly some other file utilities? Mono is pretty big though and as I recall, the mono developers are happy with their existing build system, so that would possibly take some doing. I'll take a look tonight possibly. > For tasks that will never run on mono we should separate them from the core. > We should build separate assemblies for the tasks that require Win32 > functionality. The other option is to use a compiler flag to strip out code > that will not compile on mono. It can get a little dirty, but we will need > to figure some strategy out. I think we are all open to suggestions. :) There's also the issue of linux vs win32 that's separate from mono vs .net. Would it make more sense to separate mono specific tasks into one dll and linux specific tasks, if any, into another? Core - works anywhere a compliant clr is working Win32 - only windows supported tasks, including csc and vbc Mono - mcs, mono and related tasks Linux - only linux supported tasks if any. Would anybody on the mono team likely volunteer for this? ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
