Nant is a more appropriate build tool than Ant

[GoogleCodeExporter]

It seems a really strange choice to use Ant build scripts rather than
Nant. Nant is extremely mature and has been around for years and years
(since 2000 IIRC)

In addition, Mono ships with Nant.

I've created a first stab at a Nant build script by porting from the Ant
script. There is one major problem though; it appears that although Mono
ships NUnit.Framework (and places it in the gac), Nant is unable to find
this and therefore doesn't pass the appropriate /references argument to the
compiler (mcs).

The solution to this would be to ship nunit.framework.dll with the gdata
sources and reference this from both the vs2003 and the Nant build scripts.
All projects I've worked on before have done this, and most of the projects
I found online while researching this problem do the same.

So, the attached build script has the Unit Tests build task commented out.

Original issue reported on code.google.com by rbir...@gmail.com on 8 Dec 2006 at 10:25

Attachments:

• gdata.build

[GoogleCodeExporter]

I did an alternative version of this that uses "make" instead of ant or nant ;-)

Original comment by miguel.d...@gmail.com on 10 Jan 2007 at 7:20

[GoogleCodeExporter]

From my discussions with Miguel, it does not seem to be the case that all
distributions of Mono ship Nant, hence this won't solve the issue either. I 
guess i
will create a normal make file to solve this. The one miguel submitted is a good
start (although, at least on my Mac, compiled binaries don't run...), with a few
tweaks this will probably replace the ant file. 

Original comment by fman...@gmail.com on 12 Jan 2007 at 12:38

• Changed state: ByDesign