gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaroslaw Kowalski" <j...@zd.com.pl>
Subject Re: [nant-dev] NAnt and Gump -- getting closer...
Date Tue, 07 Sep 2004 19:16:08 GMT
I don't know exactly what you're trying to achieve with Gump, but IMO things
are much easier than you think if you fully utilize NAnt's potential.

Nant is quite a portable beast today. It can run on 4 platforms (mono-1.0,
net-1.0, net-1.1, net-2.0) and compile for some more (netcf-1.0 and sscli).
The platform of your choice influences all .NET tasks and involves
platform-specific lookup and commandline parameter pasing. Many things have
been done to assure platform independence so that you can run target
multiple platforms with little to no change in your build scripts. NAnt
provides all the logic to detect the presence and location of
platform-specific assemblies and to pass them as arguments to appropriate
commandline compilers.

On windows it's possible to target all the platforms (including mono for
windows).
On Linux it's only possible to target mono-1.0.

To compile for a particular platform you simply run

nant.exe -targetframework:net-1.0 buildfile.build
nant.exe -targetframework:net-1.1 buildfile.build
nant.exe -targetframework:net-2.0 buildfile.build
nant.exe -targetframework:mono-1.0 buildfile.build
nant.exe -targetframework:netcf-1.0 buildfile.build

If you don't provide the target platform it's assumed that you want to
target the current platform you're running on (.NET 1.1 in most cases, but
can be .NET 2.0 or .NET 1.0).

Nant can be run from any directory, there's no need to invoke it in the
build file directory.
The sequence used to download, compile and install nant from CVS is very
simple:

cvs checkout nant
nant\bin\NAnt.exe install -f:nant\NAnt.build -D:install.prefix=targetprefix

I believe that all steps necessary to fully bootstrap nant from source
(including external dependencies) can be easily put in a single build file
that would be invoked by just-bootstrapped nant itself.

The build would be very simple and would just consist of <cvs-checkout>,
<nant> and <copy> tasks.

Or perhaps I am missing something... Correct me if I'm wrong.

Jarek

BTW. You may contact me on ICQ #298783166 or somewhere on IRC

----- Original Message ----- 
From: "Adam R. B. Jack" <ajack@apache.org>
To: <nant-developers@lists.sourceforge.net>; <general@gump.apache.org>;
"Stefan Bodewig" <stefan.bodewig@freenet.de>
Sent: Tuesday, September 07, 2004 6:37 PM
Subject: Re: [nant-dev] NAnt and Gump -- getting closer...


>
> > The script would need to know which framework you intend to use.  For
> > the Bourne shell script this simply means something like
> >
> > #!/bin/sh
> > mono bin/NAnt.exe
> >
> > (ignoring Rotor and DotGNU for now) but the Windows batch file is a
> > different beast.
>
> We could set a Gump parameter in the workspace and launch
> nant-%FRAMEWORK%.[sh|bat] as the script, meaning a different one per
> framework. Alternatively we could pass the framework as a parameter.
> Whichever works best for the NAnt community...
>
> regards
>
> Adam
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> nant-developers mailing list
> nant-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message