From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-02-21 07:45:01
> Jurko GospodnetiÄ wrote:
>> Hi Eli.
>>> lib name : one.ec two.c : <include>. : : <include>. ;
>>> And all is well now.
>> Glad to hear it. :-)
>> One more remark... I personally would not use <include>. here as that
>> makes presumptions (most like undocumented) on which folder you are
>> running your build from. If you really mean
>> the-folder-your-Jamfile-is-in I would rather use something like this:
>> path-constant SOURCE_FOLDER : . ;
>> lib name
>> : one.ec two.c
>> : <include>$(SOURCE_FOLDER)
>> : <include>$(SOURCE_FOLDER) ;
>> Hope this helps.
>> Best regards,
>> Jurko GospodnetiÄ
> That's unnecessary, actually. Since <include> is a "path" feature, it
> keeps track of the correct directory. That's one of the features that
> initially attracted me to boost build, since I was sick of updating
> paths every time a library changed. :-)
OK, thanks... forgot about that :-(... and got mislead by someone in
the thread using '-I.' in the actual command line.
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