[boost] Bjam build.bat does not work for msvc

From: Matthew Towler (towler_at_[hidden])
Date: 2003-04-07 05:15:20

I am using msvc6 on windows 2000.

with \boost\boost_1_30_0\tools\build\jam_src as the current directory I 
typed the command "build.bat msvc" and get the following output

D:\boost\boost_1_30_0\tools\build\jam_src>"C:\PROGRA~1\MICROS~3\VC98\bin\cl.exe"
 /nologo /GZ /Zi /ML -DNT -DYYDEBUG 
/LIBPATH:"C:\PROGRA~1\MICROS~3\VC98\LIB;C:\P
ROGRA~1\MICROS~3\VC98\MFC\LIB;C:\PROGRA~1\MICROS~3\VC98\LIB;C:\PROGRA~1\MICROS~3
\VC98\MFC\LIB;C:\Program Files\Microsoft Visual Studio 
.NET\FrameworkSDK\Lib\" k
ernel32.lib /Febootstrap.msvc\jam0  command.c compile.c execnt.c 
execunix.c exec
vms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c hash.c 
hdrmacro.c
headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c 
option.c par
se.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c 
timestamp.c v
ariable.c modules.c strings.c filesys.c builtins.c pwd.c
Command line warning D4002 : ignoring unknown option 
'/LIBPATH:C:\PROGRA~1\MICRO
S~3\VC98\LIB;C:\PROGRA~1\MICROS~3\VC98\MFC\LIB;C:\PROGRA~1\MICROS~3\VC98\LIB;C:\
PROGRA~1\MICROS~3\VC98\MFC\LIB;C:\Program Files\Microsoft Visual Studio 
.NET\Fra
meworkSDK\Lib" kernel32.lib /Febootstrap.msvc\jam0  command.c compile.c 
execnt.c
 execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c 
glob.c ha
sh.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c 
make1.c newst
r.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c 
search.c subst
.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c'
Command line error D2003 : missing source filename

I have had a look into this and have found out that this is a bug 
introduced in version 1.7 of build.bat

The problems are twofold

Firstly /LIBPATH is not a valid command line argument for cl.exe.  It 
could be made valid by putting it at the end of the command line, after 
adding a the "/link" option (which tells cl.exe to pass the rest of the 
command line to the linker).

Secondly /LIBPATH can only take a single path as an argument, if 
multiple directories are required then there must be multiple /LIBPATH 
options. %LIB% on my system is 
"C:\PROGRA~1\MICROS~3\VC98\LIB;C:\PROGRA~1\MICROS~3\VC98\MFC\LIB".

I would be interested to know if anyone has got this to work, and if so 
what their configuation was.  The check in comment for version 1.7 says 
it is to "fix" compilation for msvc but there is no detail as to what 
problem it is actually fixing.

MatthewT