Hi Nicholas,
For Visual C++, the solution task indeed relies on these environment
variables being set. I'd like to remove the need for this, but I'm not sure
if we can discover the value of each of these environment variables from the
registry in a generic way, so that we don't have to hardcode this info for
each support target framework (or version of VS).
The issues you encountered don't seem to be related to this. Can you create
two small (not 45 projects ;-)) repro's for these issues ?
Thanks!
Gert
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nicholas
Herring
Sent: maandag 16 april 2007 8:35
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] VS2003 <solution> outputdir and Bad VCC options
Hello,
I just recently tried to migrate one of our projects from Ant to NAnt. We
have a solution that contains 45 projects and is all unmanaged C++. I have
two main issues:
1.) I have to specify <outputdir> in the solution tag. The reason that I
am required to: when I try to build the solution without it NAnt reports
that it is unable to determine the output directory. The other problem here
is that I now have to go through 45 projects and modify 6 configurations per
project for this to work correctly. What can I do to help NAnt determine
what the output directories are automatically, also, is there a project name
variable that I can place in the solution tag to possibly rebuild these
output directories through NAnt? I ask because none of our projects has a
common output directory.
2.) After I modified a few projects, I get to one of our procedural
projects and I get this error:
"fatal error C1189: #error : "Bad VCC option: C++ exception handling must
be enabled""
I don't understand why I get this error because when I run devenv command
line in all configs with build/rebuild combinations I don't get this error.
Basically, I only have this error when using NAnt. Any ideas why this would
be an issue?
A disclaimer to the setup:
I had to mimic vsvars32.bat in the build file in order to get NAnt to find
cl.exe. Like so:
<setenv>
<variable name="VSINSTALLDIR" value="C:\Program Files\Microsoft Visual
Studio .NET 2003\Common7\IDE"/>
<variable name="VCINSTALLDIR" value="C:\Program Files\Microsoft Visual
Studio .NET 2003"/>
<variable name="FrameworkDir"
value="C:\WINDOWS\Microsoft.NET\Framework"/>
<variable name="FrameworkVersion" value="v1.1.4322"/>
<variable name="FrameworkSDKDir" value="C:\Program Files\Microsoft
Visual Studio .NET 2003\SDK\v1.1"/>
<!--<variable name="VCINSTALLDIR=%VSINSTALLDIR%-->
<variable name="DevEnvDir" value="%VSINSTALLDIR%"/>
<variable name="MSVCDir" value="%VCINSTALLDIR%\VC7"/>
<variable name="PATH"
value="%DevEnvDir%;%MSVCDir%\BIN;%VCINSTALLDIR%\Common7\Tools;%VCINSTALLDIR%
\Common7\Tools\bin\prerelease;%VCINSTALLDIR%\Common7\Tools\bin;%FrameworkSDK
Dir%\bin;%FrameworkDir%\%FrameworkVersion%;%PATH%;"/>
<variable name="INCLUDE"
value="%MSVCDir%\ATLMFC\INCLUDE;%MSVCDir%\INCLUDE;%MSVCDir%\PlatformSDK\incl
ude\prerelease;%MSVCDir%\PlatformSDK\include;%FrameworkSDKDir%\include;%INCL
UDE%"/>
<variable name="LIB"
value="%MSVCDir%\ATLMFC\LIB;%MSVCDir%\LIB;%MSVCDir%\PlatformSDK\lib\prerelea
se;%MSVCDir%\PlatformSDK\lib;%FrameworkSDKDir%\lib;%LIB%"/>
</setenv>
Does anyone have any input on these problems? Does it all stem from the fact
that I had to mimic vsvars32.bat?
Any insight is appreciated,
-Nick
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
