From: Zbynek Winkler (zwin_at_[hidden])
Date: 2004-07-15 06:16:09
Vladimir Prus wrote:
>>>What you propose that
>>>4. It's possible to refer to other Jamfile using first symbolic project
>>>id and then filesystem path relative from that.
>>What I propose is that:
>> project IDs are bracketed (or something).
>> filesystem paths are un-bracketed
>Ok, I understand. I wonder though, why nobody complained about it yet....
Maybe not that many people are using this stuff? I don't know... What I
did was to assign id equal to the filesystem path and forgot about all
this id/path distinctions. I did get the fact that I need to use '//'
when I refer to a target and that was basicaly it. I didn't need to know
much else. However, I remember that my beginings with bjam were not so
much fun and it took time before I got grasp of everything.
One of the problems I had was related to the target referencing. Suppose
I have a directory 'mylib' in my project root and Jamfile in it that
specifies target 'mylib'. While in the same Jamfile using just 'mylib'
where the target needs to go is just fine. OTOH in a different Jamfile I
need to use 'mylib//mylib' to refer to the same target. It took me some
time to figure this out (simple 'mylib' outside of the original Jamfile
refers to all targets defined in that Jamfile).
I find this a bit strange but I see no alternative that would be better.
I guess it is just something 'to know' ;-).
-- http://zw.matfyz.cz/ http://robotika.cz/ Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic
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