[Mono-dev] gendarme: nant build files
russell at russellsprojects.com
Mon Aug 28 18:14:06 EDT 2006
[Accidentally sent this to Sebastien only the first time...]
I've used NAnt quite a bit at work to build
continuous integration / automated distribution build systems for a few
projects here. I'll take a look at getting a patch that does this for
Gendarme tonight. The only sticking point will be that it needs to
build on both Windows and Linux systems without modifications to the
build files themselves. NAnt officially supports Mono 1.0 and 2.0
profiles, so perhaps it won't be that "magic" to get this to happen.
addition, VS2005's native project format uses MSBuild (part of the .NET
2.0 FCL, if I'm not mistaken). Is there any status on the stability or
completeness of Mono's implementation of the MSBuild system? It'd be
pretty nice to have only two build systems to maintain - make for
Linux/Cygwin, or MSBuild for Linux/Cygwin/VS.NET/Windows CLI. I don't
have even a working knowledge of MSBuild in general, however, so this
may be pure pie-in-the-sky wishing on my part :)
From: Sebastien Pouliot <sebastien.pouliot at gmail.com>
Sent: Monday, August 28, 2006 5:37 PM
To: Christian Birkl <christian.birkl at gmail.com>
Subject: Re: [Mono-dev] gendarme: nant build files
On Mon, 2006-08-28 at 23:13 +0200, Christian Birkl wrote:
> Since i'm a windows user (I don't believe I've said this loud) it is
> really hard for me to run the Makefile based build.
Using the Makefile should work using cygwin (and I can't believe I'm
suggesting cygwin to someone ;-)
> Also MonoDevelop is just available for *nis (last time i checked) so
> no chance for us windows developers to build gendarme out of the box.
> I get your point with the outdating - but currently as a windows
> developer you just get the source and need to manually create either
> VS projects or nant build files. By providing at least nant build
> files one may easier begin patching gendarme than without.
I understand this issue, which is why I'm open to a third build system.
But, like I said, I don't have any NAnt knowledge myself so someone else
needs to step up for it ;-)
Why ? because once this is in SVN/tarballs people will expect it to be
maintained (even if I write "use at your own risk" in the README).
> Since I'm not that involved in other projects - how do other handle
> this issue with "build files"?
I suspect they each build their own project file (e.g. in VS.NET) and
yes this is clearly inefficient.
Now one of my computers is a WinXP box with VS.NET 2005, so I may take
the time to create a VS.NET solution in the future as, somehow, it make
sense "test-wise" and commit it into SVN (if there is demand for it).
But I'm still open to a contributor-supported NAnt build ;-)
> 2006/8/28, Sebastien Pouliot :
> Hello Christian,
> On Mon, 2006-08-28 at 22:47 +0200, Christian Birkl wrote:
> > Hello all,
> > attached a NAnt build file for build and running gendarme.
> Two things
> > bug me currently which should be corrected by someone who
> has more
> > experiences with nant build files:
> We already have 2 build systems (Makefile and MonoDevelop) for
> I don't mind adding a third one, but I don't want to maintain
> it ;-)
> Will you maintain it ? (*)
> (*) which also means that it will get deleted if it gets
> outdated and
> not updated for a while (i.e. after I get angry few emails
> about it ;-)
> > - Mono.Cecil location must be specified as property (a
> dynamic lookup
> > in gac/pkg-config would be nice)
> > - same with nunit.framework if you want to run the unit
> I don't know much about NAnt myself. Maybe Gert could help you
> with this ?
> p.s. let fix those issues before committing the build file (as
> *really* want running the unit tests to be as easy as
> Sebastien Pouliot
> Blog: http://pages.infinit.net/ctech/
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list