Title: RE: RE: [Nant-users] Building C++ with differenct configurations
I do something similar.
We capture the stack trace in our exception handling.
With SYMBOLS the stack trace contains a line number in addition to the usual message.
Very handy when something is difficult to recreate
[EMAIL PROTECTED] wrote:
Although your right, whats the point of a debug build on your build
server?
We do it because the way we use NCover, it needs to have the debugging
symbols.
Gary
---
SF.Net email is sponsored by: Discover Easy L
Ok I get your point... We're using direct calls to devenv.exe instead of compiling everything ourselves... This leads to a couple of issues (one is scalability!) but for us it was finally the best option.
In your situation would it be acceptable to have two separate targets in one build script ?
" />
<link output ="${output.directory}\${output.file}"
options="${options}" >
And this get
lot more complicated for cl.exe, which is why i am thinking having a separate
NAnt script.
Although your
right, whats the point of a debug build on your build server?
T
Hi Trevor
I build both in the same NAnt script using a for loop like:
foreach>
then in the build target :
[Nant-users] Building C++ with differenct configurations
Title: Message
Hi,
what does everyone do to build release and debug versions of your
c++ projects. Is it preferred to have separate NAnt scripts for each, or should i just set different compiler options in one script, depending on which configuration is being built?
Thanks
Trev
---
