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.
The first step in getting "Mono Support" is in defining what is needed and should be included for Mono. It would be good to list what parts of Mono are missing, and what we need. Maybe it is too early to try to support mono, maybe not. 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. :) ----- Original Message ----- From: "Philip Nelson" <[EMAIL PROTECTED]> [snip] > What parts of NAnt? I had gotten NAnt.exe to partially run with the last > release of Mono but there are serious parts missing, particularly in Xml > support that could make this difficult at this time. And how do you account for > core tasks that would never run on Mono, if at all? ------------------------------------------------------- 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
