bin-stage ignoring ALL_LOCATE_TARGET?

From: Raoul Gough (raoulgough_at_[hidden])
Date: 2003-10-07 05:07:41

I updated to the latest CVS last night, and the build is now putting
all of the bin-stage directories back in the source tree, ignoring the
ALL_LOCATE_TARGET setting. All other binaries go into the correct
(separate) build tree, but not bin-stage. Platform is MinGW with a
from-source MinGW bjam build.

e.g. (lines wrapped manually) after deleting the bin-stage directories:

D:\CVS\boost\boost> tools\build\jam_src\bin.ntx86\bjam -d2
-sTOOLS=mingw -sALL_LOCATE_TARGET=d:\build\boost

...found 3456 targets...
...updating 15 targets...
MkDir1 libs\python\build\bin-stage

mkdir libs\python\build\bin-stage

FileClone libs\python\build\bin-stage\boost_python_debug.dll

copy d:\build\boost\bin\boost\libs\python\build\boost_python.dll
\mingw\debug\boost_python_debug.dll libs\python\build\bin-stage
\boost_python_debug.dll

1 file(s) copied.
FileClone libs\python\build\bin-stage\boost_python_debug.lib

copy d:\build\boost\bin\boost\libs\python\build\boost_python.dll
\mingw\debug\boost_python_debug.lib libs\python\build\bin-stage
\boost_python_debug.lib

1 file(s) copied.

[etc...]

Is this by design? I would like to put all binaries outside of the
source tree, and I was hoping that this is what ALL_LOCATE_TARGET
would do.

-- 
Raoul Gough.
(setq dabbrev-case-fold-search nil)