Milestone 4 Preview 1, Response files & Borland compiler

From: Ian Berthon (ian_at_[hidden])
Date: 2003-06-23 08:26:12

Hi,

I'm new to the list and new to bjam, so please accept my apologies if 
I've made a newbie error but I think there might be a problem with the 
response file processing in Boost.Build v2.

Here is my Jamfile:-

project test ;

lib boost_filesystem : : <name>libboost_filesystem 
<search>f:/library/boost_1_30_0/libs/filesystem/build/bin/libboost_filesystem.lib/borland/debug/runtime-link-dynamic 
;

exe test : main.cpp boost_filesystem ;

When I run BJAM -d2 I get the following output:-

...found 14 targets...
...updating 4 targets...
borland.compile.c++ bin\borland\debug\main.obj

"bcc32" -j5 -g255 -q -c -P -w -Ve -Vx -a8 -b- -v -Od -tWC -tWR 
-tWC -WM- -I"bin\borland\debug" -I"" -o"bin\borland\debug\main.obj" 
"main.cpp"

main.cpp:
text-action bin\borland\debug\test.rsp

echo 
-Lf:\library\boost_1_30_0\libs\filesystem\build\bin\libboost_filesystem.lib\borland\debug\runtime-link-dynamic 
>> bin\borland\debug\test.rsp

text-action bin\borland\debug\test.rsp

echo -llibboost_filesystem.lib >> bin\borland\debug\test.rsp

response-file-1 bin\borland\debug\test.rsp

echo "bin\borland\debug\main.obj" > "bin\borland\debug\test.rsp"

borland.link bin\borland\debug\test.exe

set "PATH=;%PATH%"
"bcc32" -v -q -v -tWD -v -tWC -tWR -tWC -WM- -L"" 
-e"bin\borland\debug\test.exe" @"bin\borland\debug\test.rsp"

Error: Unresolved external 'boost::filesystem::path::path(const char 
*, boost::filesystem::path_format)' referenced from 
F:\PROJECTS\FREEDB\TEST\BIN\BORLAND\DEBUG\MAIN.OBJ
Error: Unresolved external 'boost::filesystem::path::path(const char 
*)' referenced from F:\PROJECTS\FREEDB\TEST\BIN\BORLAND\DEBUG\MAIN.OBJ
Error: Unresolved external 'boost::filesystem::path::operator 
/=(const boost::filesystem::path&)' referenced from 
F:\PROJECTS\FREEDB\TEST\BIN\BORLAND\DEBUG\MAIN.OBJ
Error: Unresolved external 
'boost::filesystem::path::native_file_string() const' referenced from 
F:\PROJECTS\FREEDB\TEST\BIN\BORLAND\DEBUG\MAIN.OBJ
Error: Unresolved external 
'boost::filesystem::path::native_directory_string() const' referenced 
from F:\PROJECTS\FREEDB\TEST\BIN\BORLAND\DEBUG\MAIN.OBJ
...failed borland.link bin\borland\debug\test.exe...
...failed updating 1 target...
...updated 3 targets...

Looking at the 'echo' lines above, it looks like the first couple of 
echoes are appending to the response file but the final one is 
overwriting the file, causing the library info to be missing from the 
link step (hence all the unresolved external errors).

Additionally and, I guess, specific to the Borland compiler, it's using 
the gcc '-l' syntax for the library which results in an 'Incorrect 
command line option' error. I had a quick look at BORLAND.JAM but 
couldn't figure out where it's going wrong, could someone please point 
me in the right direction?