[MonoDevelop] Autotools integration?

Michael Lausch mla@lausch.at
Wed, 15 Dec 2004 14:44:58 +0100


On Wed, 2004-12-15 at 04:56 -0800, Peter Johanson wrote:
> On Wed, Dec 15, 2004 at 10:02:37AM +0100, Michael Lausch wrote:
> > On Tue, 2004-12-14 at 21:47 -0800, Todd Berman wrote:
> > > On Tue, 2004-12-14 at 21:13 -0500, Miguel de Icaza wrote:
> > 
> > > >     Hence organically grown, pkg-config based, and the configure and
> > > > Makefiles generated from our internal XML "Solution" format is the right
> > > > path to go.
> > > > 
> > > > Miguel.
> > > 
> > > 
> > > There is already the beginnings of an implementation of this in
> > > MonoDevelop. However, to not conflict with existing makefiles, the
> > > makefile created is named Makefile.SolutionName and is easily runnable
> > > via a make.sh file created in your toplevel directory.
> > 
> > and using NAnt for this? the advantage of NAnt is that it's easier to
> 
> See the previous statement about NAnt being more than non-trivial to get
> installed/working currently.

the current rc1 release has exacvtly two issues, with respect to mono.
one is a trivial reordering in the config file, to bring the runtime
requirements in the "correct" order, the other is a compiler issue (i
assume), which can be resolved by a trivial patch. I might be able to
provide a mono 1.1.x compiled RPM package, if there's interest in this.
I'm not a great fan of NAnt (got my fingers burned with Ant much to
often), but it's the most cross platform thing. cygwin support for
windows to get make running is more of a pain than to apply the two
patches to NAnt, i think. And with carefuyl written NAnt templates
nearly all of autoconf/automake/make can be implemented.


> 
> -pete
> 
-- 
Michael Lausch <mla@lausch.at>