Boost logo

Boost-Build :

From: Deane Yang (deane_yang_at_[hidden])
Date: 2005-11-30 13:15:01

I had posted a fairly incoherent message about this problem before; I'd
like to try to post something a little clearer. If anyone can help me
with this, I'd be really grateful.

I'm building a DLL on Windows using bjam. If I omit the <runtime-link>
feature, it all works fine without any problems.

If I add "<runtime-link>static", then it appears that the linker
successfully builds the DLL, as well as the .lib and .exp files, but
does not generate a manifest file. So the subsequent call to mt.exe
fails, because no manifest file is found. bjam then deletes the files
generated by the linker.

I've examined the calls to the linker, and it looks to my naked eye that
they are exactly the same, except that with the runtime-link-static set,
  everything is down one level deeper in the directory hierarchy.

For the record, here is what bjam says it's calling (the response files
also appear to be identical, except for the directories):

(without <runtime-link>static)
call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86 >nul
link /NOLOGO /DEBUG /subsystem:console /DLL
     mt -nologo -manifest

(without <runtime-link>static)
   call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat"
x86 >nul
link /NOLOGO /DEBUG /subsystem:console /DLL
     mt -nologo -manifest

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at