From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-02-05 17:35:23
> Within Microsoft Visual Studio I successfully built the hello.cpp file from
> the SmartWin++ Library. Here is the compiler command line:
> /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_VC80_UPGRADE=0x0710" /D
> "_MBCS" /Gm /EHsc /RTC1 /MTd /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W3 /nologo /c
> /Wp64 /ZI /TP /errorReport:prompt
> For comparison, here's the command line (reproduced from my original
> message) apparently used by the build.bat file in jam:
> cl /nologo /RTC1 /Zi /MTd /Fobootstrap/ /Fdbootstrap/ -DNT -DYYDEBUG -wd4996
> kernel32.lib advapi32.lib user32.lib /Febootstrap\ jam0
Ok, here's what I suppose could have happened.
You're using a Platform SDK that did not come installed with your
development environment and and you installed it additionally it
integrated itself into the Visual Studio IDE but did not update its
vcvarsall.bat batch file.
That is the batch file started by build.bat to get the correct
environment set up for using Visual Studio tools from the command line.
Look into that batch file (or just run it) or whatever batch file it
forwards to and make sure it sets up the correct library search settings.
I do not have VS8.0 installed here so I can not give you more precise
directions but on VS7.1 the corresponding vcvars32.bat file is located
in %VS71COMNTOOLS%/vcvars32.bat and it sets LIB & INCLUDE environment
variables to be used by cl.exe.
Hope this helps,
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk