[Mono-devel-list] NAnt revisited
Jaroslaw Kowalski
jaak at zd.com.pl
Mon Dec 29 12:42:14 EST 2003
Some pointers:
1. There's no <mcs> task anymore. <csc> is used for both csc.exe and
mcs.exe.
2. NAnt supports the concept of "frameworks" which allow you to specify the
CLI which should be used for build. In theory the same build script can be
used for mono, .NET, sscli, portable .net or any other CLI. In practice
there are some small bugs that make this quirky, but things are getting
better all the time. This feature works great on Windows where it can be
used to select among .NET 1.0, .NET 1.1, .NET 1.2 and SSCLI.
3. I use NAnt (from CVS) on Linux (Fedora Core 1) with Mono(CVS) and have no
problems. I am successfully able to build my projects so that they work on
Linux and Windows. <nunit2> support is there and is usable, but there are
still some minor issues.
4. In general: don't use NAnt from "mcs" - it's rather old. Use nant from
http://nant.sourceforge.net/.
5. After you download nant form CVS you have to rebuild it for mono using
standard "make". After you have the NAnt bootstrapped (binaries go to
"build/..." directory, you can rebuid itself on Linux using exactly the same
script as on Windows.
Should hou have any problems, join nant-users at lists.sourceforge.net and ask
your questions there.
Jarek
----- Original Message -----
From: "Jason King" <jason.king at profox.co.uk>
To: "'mono-devel mailing list'" <mono-devel-list at lists.ximian.com>
Sent: Monday, December 29, 2003 5:46 PM
Subject: [Mono-devel-list] NAnt revisited
> Hiya all.
>
> Try as I might, I can't seem to get NAnt and Mono 0.28 to work together.
> Does anyone have any pointers for me? It would be really useful if some
> kind soul could get NAnt working again complete with the MCS and NUnit2
> tasks.
>
> Have a good new year.
> Jase
>
> Regards,
> Jason King
> Profox Systems Ltd
>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
More information about the Mono-devel-list
mailing list