<property name="release.options" value='/INCREMENTAL:NO' />
<property name="common.options" value =' /DELAYLOAD:"mtxex.dll" /NOLOGO /DLL /DEF:".\${project.name}.def" /IDLOUT:"_${project.name}.idl" /DEBUG /PDB:"${build.dir}\${project.name}.pdb" /SUBSYSTEM:WINDOWS /IMPLIB:"${build.dir}\${project.name}.lib" /MACHINE:X86 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib common.lib' />
<if test="${config=='release'}">
<property name="options" value="${common.options} ${release.options}"/>
</if>
<if test="${config=='debug'}">
<property name="options" value="${common.options} ${debug.options}"/>
</if>
<echo message="${options}" />
<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?
Trev
-----Original Message-----
From: Thibaut Barrère [mailto:[EMAIL PROTECTED]
Sent: 28 June 2005 16:40
To: Moody, Trevor: IT (LDN)
Cc: nant-users@lists.sourceforge.net
Subject: Re: [Nant-users] Building C++ with differenct configurationsHi TrevorI build both in the same NAnt script using a for loop like:<foreach property ="configuration" item="String" in="Debug,Release" delim=","><call target="build"/>
</foreach>
then in the build target :
<property name="commandLine" value="${solutionFile} /build ${configuration} /out ${logfile}"/>
As a sidenote I'll add that we are going to stop building the debug builds here (c++ projects are taking the biggest amount of build time, and most people tend to compile locally when willing to debug).kind regards
Thibaut Barrère
2005/6/28, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: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?ThanksTrev
------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.
------------------------------------------------------------------------