Fw: [boost] thread library won't compile - win32

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-18 06:53:32

Hmm, there is a bug somewhere.

I knew we were getting some extra directories in the path in some of these
cases, but this is ridiculous. For one thing, your example below contains
"stlport-iostream" and "stlport-iostream-off", both clearly bugs.

Furthermore, in this part of the substring

'debug-symbols-on\exception-handling-on\inlining-off\optimization-off\rtti-
on\runtime-build-debug\runtime-link-dynamic\stlport-cstd-namespace-std'

Only runtime-link-dynamic should be showing up in the path. The rest is
covered by feature defaults the properties of the debug build variant.

Rene, we may have reached the breaking point where you have to figure out
how to get rid of those spurious subvariant directories from v1.

-Dave

----- Original Message -----
From: "Tom Wells" <tomw_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, July 18, 2002 6:16 AM
Subject: [boost] thread library won't compile - win32

> hi everyone,
>
> i'm quite new to using boost and haven't had any problems using it with
gcc
> in linux, but i can't seem to get the threads library to compile in
windows
> 2000 using msvc6 with stlport (with stlport-iostreams on).
>
> this is the problem:
> when i try running 'bjam -sTOOLS="msvc-stlport" -sBUILD="stlport-iostream
> on"' in the <boost_dir>\libs\thread\build directory it tries to make a
whole
> bunch of directories with names based on the sub-variants such as:
>
>
..\..\..\libs\thread\build\bin\libboost_thread.lib\msvc-stlport\stlport-ios
t
>
ream\debug-symbols-on\exception-handling-on\inlining-off\optimization-off\r
t
>
ti-on\runtime-build-debug\runtime-link-dynamic\stlport-cstd-namespace-std\s
t
> lport-iostream-off
>
> the logic seems to be good, but the problems seems that windows can't
handle
> a directory tree with more than 256 characters, so it bombs out with
errors
> like 'The directory or file cannot be created' and 'The filename or
> extension is too long'.
>
> i had a look at the Jamfile (i've never used jam before) and tried to see
> where it creates these directories, but its quite cryptic and i couldn't
> find anything at all. i've read the docs and build instructions looking
for
> some way to override this behaviour, but i can't find a thing.
>
> any suggestions? please help!
>
> Tom Wells