-developers@lists.sourceforge.net
Subject: Re: [nant-dev] NAnt status report [2010-02-14]
Hi Gert,
Thanks for the information. I apologize if I appear to be stumbling a bit.
More comments below... you feedback is much appreciated.
Charles
- Original Message
From: Gert Driesen gert.drie
status report [2010-02-14]
Hey Charlies,
Some quick responses:
NAnt.build
==
I don't consider NAnt.build internal. The nightly.xml and release.xml are
internal though, as these are used to build releases and nightly builds (or
CI).
In general, one should be able to build NAnt using
: dinsdag 16 februari 2010 21:35
To: Gert Driesen; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] NAnt status report [2010-02-14]
Gert,
A few more questions? Hope you don't mind ... :)
Charles
- Original Message
From: Gert Driesen gert.drie...@telenet.be
To: Charles
Hi Gert,
The part that really confused me was the fact the description inside README.txt
seems to indicate the 'install' target must be used.
make install MONO= MCS=csc prefix=installation path [DESTDIR=staging path]
However, I just want to build it (not install it). After taking a closer
@lists.sourceforge.net
Sent: Sun, February 14, 2010 11:10:00 PM
Subject: RE: [nant-dev] NAnt status report [2010-02-14]
Hey Charles,
That function - which I consider to be internal - may indeed not be part of
any official release.
That is sort of what I figured and worried (see below).
So
FYI.
Based on the information from Gerry, I spend the past week trying to 'build
NAnt with NAnt'. The first order of business was to understand how the whole
thing works. After diving around at the code (adding more comments along the
way), I focused on NAnt.build...
(Long story short)
After
-developers@lists.sourceforge.net
Subject: [nant-dev] NAnt status report [2010-02-14]
FYI.
Based on the information from Gerry, I spend the past week trying to 'build
NAnt with NAnt'. The first order of business was to understand how the whole
thing works. After diving around at the code (adding more
