From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-07-10 17:27:13
[2002-07-10] gclbb-jamboost_at_[hidden] wrote:
>In article <20020710151726-r01010800-97aeb38f-0860-0108_at_220.127.116.11>,
>Rene Rivera <jamboost_at_[hidden]> wrote:
>>[2002-07-10] gclbb-jamboost_at_[hidden] wrote:
>>>In article <019401c225e0$bebcee30$6601a8c0_at_[hidden]>,
>>>David Abrahams <jamboost_at_[hidden]> wrote:
>>SOME_VAR = ; # no-value
>>ANOTHER_VAR = $(SOME_VAR)/some/stuff ; # still no-value
>Ok, so then:
> COMO_BIN_DIRECTORY ?= $(COMO_BASE)$(SLASH)bin$(SLASH) ; // AA
>COMO_BIN_DIRECTORY ?= "" ; // BB
>set it to "" if COMO_BASE is not set, because then line BB doesn't
>do the assignment to COMO_BIN_DIRECTORY?
>>And when doesn't it not work?
>It usually works when the lib is a C library or a non-template
>based class library, but it is requires instantiations it'll
>circumvent that process (which may be ok in some cases,
>but generally not).
I'm familiar with that problem. GCC has similar contraints.
>>As it looks to me it
>>actually does that on Windows, but in addition also adds it
>>to the command line explicitly.
>Ah, yes, I forgot I thought I saw that 2 days ago when I looked.
>That's why it appears to work. This is probably harmless in
>terms of soemthing going work, but as it's extra, probably
>best to take out, especially if functionality is ever given
>to LIB (and there might be eventually).
So it would be more appropriate to include such things in the command line
only? Therefore leaving it to como to set the environment vars for the
backend accordingly. Which is why I think LIB is set for Windows, so that
the VC backend can see those.
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk