Hello,
From the same source files, I need to create a couple of builds for
different frameworks, different debug values, ... and 1 with a doc.
So I define the main build:
Then, for each build I want to create, I set-up the properties and do a
to "build":
This way works fine, except to gen
It looks like when running the task over a set of files in a
particular directory, the task is run on each file in alpha order. For
example, running the following nant task:
Where d:\foo contains the following files:
00_text.txt
01_text.txt
10_text.txt
100_te
In VS.Net 2003 it appears to default to
/O2.
Ray
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gert
DriesenSent: Wednesday, April 20, 2005 11:31 AMTo:
[EMAIL PROTECTED]; nant-users@lists.sourceforge.netSubject: RE:
[Nant-users] /O2 is not set when using NANT
Ray,
I
Ray,
If I'm not mistaken, the default optimization for VC++ 7.0
projects was not /02. If you can verify this (I don't have VS 2002 installed),
then we can fix this the right way.
Better submit a bug report for this to allow us to track
it.
Gert
From:
[EMAIL PROTECTED]
[mailto:[EM
In a standard C++
project the /O2 option is passed in during a standard release build.
However, unless you've mucked with the Optimization settings the setting is not
set in the project file it is the default. (I.e. the Optimization
attribute does not exist for the VCCLCompilerTool.) As
Steve,
Can you submit a bug report for this and attach a small
repro ?
Thanks !
Gert
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve
BrennanSent: maandag 18 april 2005 15:34To:
nant-users@lists.sourceforge.netSubject: [Nant-users] C++ project
link
Hi Jason,
There was indeed a packaging screw-up in the 0.85 RC3
release (sorry about that). Thanks for bringing this to my
attention.
I don't have time to correct this now, but it will
definitely be corrected in the final release. Until then, please use a
recent nightly build.
Sorry
After upgrading to rc3, my tasks started
to break due to the new log4net 1.2.9 (1.2.1.40796). It looks like when
the task execs out to my TortoiseCVS cvs.exe, I get an
assembly reference mismatch. I prefer to use my external cvs.exe instead
of the packaged dll.
Anyone have any thoughts
I
have two C++ projects that compile and link correctly under Visual Studio.
One project uses a class defined in the other. Under Nant 0.85 nightly
build from 4/14, the build ends with a linker error. I get the following
output:
[solution]
Starting solution build. [solution] Loading
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Morris, Jason
> Sent: woensdag 20 april 2005 16:24
> To: nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] Has anyone tried the new task?
>
> I got it from this url for the nightly bu
I got it from this url for the nightly build docs task reference:
http://nantcontrib.sourceforge.net/nightly/latest/help/tasks/codestats.h
tml
I would have thought that the nightly and latest docs would have been
the same so close to after rc3.
>-Original Message-
>From: Gert Driesen
Hi Bill,
I'll take a short break (vacation) and if no serious issues surface by the
time I get back, I might release 0.85 around the 5th of May (or so).
Until then, make sure you try the latest nightly build as I've introduced a
task performance enhancement, and I want to make sure its not
causi
I know that RC3 has only just been release (thanks for the effort guys), but
is there any projected time scale on the proper 0.85 release? I would guess
that at RC3 there isn't much wrong. Is RC3 going to become the release or
are there any more iterations planned?
I wish to upgrade our developm
For anyone who may run into this problem...
I was running VSS 6.0c. After upgrading to VSS 6.0d the problem was fixed.
Thanks to anyone who helped.
Mark
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 10:36 PM
To: Rainey, Mark (Cleveland)
What may be cleaner than directly writing the child build scripts using
the task is to use XML/XSLT to template your build
scripts...
http://nant.sourceforge.net/release/latest/help/tasks/style.html
It would probably yield a more maintainable script in the long run,
since XSLT should be much simp
Selke, Anthony wrote:
Ouch. I really hoped to avoid building the file from scratch (hence the
tag). What about the node? I have the following:
Actually I've just done a similar thing- dynamically generating a nant
script (although mine was for customised remote application installs.
What you
16 matches
Mail list logo
