Shoot - I must sheepishly reply that this actually works
correctly in the latest nightly build. (I had a pre release cand. 2 build
I was using...)
Sorry for the chatter...
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ray
JohnsonSent: Friday, June 10, 2005 3:45 PMTo:
It appears that
PreBuild events when run in Nant does not exactly run pre-build. We have
as a pre-build step two commands that do the following:
1) delete a .dll the
project uses as a reference
2) runs the tlbimp
command to recreate the DLL
If the DLL does not
exist (because this nev
It would be really
nice if when using the tag on a solution that includes
Post-build events, if the attempted script could be displayed when running (at
least in verbose mode, or at least when there is a failure in verbose mode).
We use a fair amount
of post-build events and we find t
Is there a facility to look at a web project and "copy" the files marked as
"Content" to a given location? This is kind of a deployment of a web
project - but we need to deploy to an intermediate directory rather than an
IIS install.
We could, of course, copy file patterns. However, one thing w
This may be due to code optimization settings. We have seen this as well
where the "default" optimizations (and thus some of the compiler flags) are
different between Nant and different versions of VS.Net.
We worked around this my explicitly setting the use of certain flags in
VS.Net. We did th
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
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
I think you will find this fixed in the latest nightly builds. (I had the
same problem a few weeks back...)
Ray
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, April 11, 2005 6:47 AM
To: nant-users@lists.sourceforge.net
We have noticed that
the size of the binary build using the nant tag is larger than
the binary built for a .exe with the VS.Net solution. I'm trying to get
figure out what could be different and have a couple of
questions:
1) Does show ALL the compiler flags that will be passed to the
Is there a way to
override the preprocessor definitions in a C++ project when using the
tag?
Ray
I finally got around to testing this. Relative paths
do seem to work much better for the C++ includes and the bost build event.
Thanks!
There is one place relative paths still appear broken,
however. That is in Resources->General->Additional Include
Directories. Again, I can work aro
Are you using relative paths in your commands? We had
problems when we did that. Try basing it off a macro so it has an absolute
path. Of course, changing the "copy" to an "echo" will help you debug the
problem...
ray
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
S
I had to add a bunch of paths to my INCLUDE and LIBS environment variables
to get it working. I had trouble getting the path passed correctly into
nant. I ended up with something like this:
It doesn't appear
that the tag understands the Configuration manager
settings. Is this true, or do I need to do something to tell it to use
them?
FYI, the
Configuration manager has info about when a given Configuration is selected to
build what projects should or should not be built,
Thanks. I've done that (request id = 1170100). I also suggested the possible line of code
that needs to be fixed. I tried it in a copy of the Nant source and it
seemed to work. However, i haven't tested it to see if it would affect
anything else...
ray
From: Gert Driesen
[mailto:[E
I tracked down a bug
related to Macro expansion of VS.Net variables within NANT. The symptom I
was seeing was that macros like $(TargetName) and other target related macros
were empty (null). Obviously, this broke various asspects of the
build.
I eventually was
able to debug the probl
uilt? Building this config
works fine in VS.Net. Any clue what I might be doing wrong?
Ray
-Original Message-
From: Ray Johnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 23, 2005 11:04 AM
To: 'Gert Driesen'; 'nant-users@lists.sourceforge.net'
Subject: RE: [Nan
build...
Ray,
Can you verify whether the name of the build configuration that you
specified on the task matches a build configuration for the
project(s) that you're building ?
A repro for this issue is definitely welcome.
Gert
----- Original Message -
From: "Ray Johnson" <[EM
C:\src\devtrunk\FullTilt\FT_Client>\src\nant-0.85-nightly-2005-03-22\build\net-1.1.win32\nant-0.85-debug\bin\NAnt.exe
debug_proNAnt 0.85 (Build 0.85.1908.0; dev; 3/23/2005)Copyright (C)
2001-2005 Gerry Shawhttp://nant.sourceforge.net
Buildfile: file:///C:/src/devtrunk/FullTilt/FT_Client/clie
We are trying to get
a large set of C++ projects working under NANT. I'm seeing a big problem
with relative paths. In many of our projects we have library references
(Linker->General->Additional Library Directories) that use relative paths
to other parts of our source tree. Unfortunatel
20 matches
Mail list logo