Re: [boost] another bjam question

From: John Maddock (john_at_[hidden])
Date: 2004-08-28 05:33:48

> When I build and run config_info using msvc-stlport I get the output below
> which doesn't seem correct. I get no reference to stlport.
>
> When I investigate the bjam output I find (for another test) I find that 
> the
> following is being used for the command line:
>
> "cl" /Zm800 -nologo /EHsc -c -D_STLP_DEBUG=1
> -D_STLP_DEBUG_UNINITIALIZED=1 -D_STLP_USE_DYNAMIC_LIB=1 /Z7 /Od /Ob0 
> /EHsc
> /GR /MDd -I"C:\BoostMainCVS" -I"c:/Program Files/microsoft visual
> studio\vc98\include" -I"c:\STLport-4.5.3\stlport"
> -Fo"..\..\..\bin\boost\libs\config\test\no_ded_typename_fail.test\msvc-stlpo
> rt\debug\threading-multi\no_ded_typename_fail.obj"
> -Tp"..\..\..\libs\config\test\no_ded_typename_fail.cpp"
>
> This indicates that the Microsoft native include is specified BEFORE the
> STLPort one. This would explain why the config_info doesn't reflect the
> STLPort usage.
>
> Can someone tell me what I should be doing differently?

I don't know, but the dmc toolset is broken for the same reason. Actually 
this seems to me to be a bad design decision: why would the compilers 
include directory be present on the command line at all? If my compilers 
environment has been modified to place some other directory first (for 
example in vcvars32.bat) then why would bjam subvert that?

John.