From: Johannes Brunen (JBrunen_at_[hidden])
Date: 2004-11-11 11:34:31
unfortunately I'm out of office until next monday. I will be offline until than.
Thank you very much for your patience!!!!
Two questions however.
At first is it that uncommon to have such long include pathes at all?
Secondly, is there a generic way to name a(n) (include) path in a root jam file and
evaluate that name in a subproject jamfile.
For instance: subproject1 and subproject2 are at completly different placesin the root-tree.
## Something like that
MyPath = ./grafic/grafic/variant/ ;
some subproject1: jamfile
project some-subproject1 : requirement <incude>$(MyPath)/opengl ;
some subproject2: jamfile
project some-subproject2 : requirement <incude>$(MyPath)/opengl ;
The point I have in mind is the relative part of the path. Otherwise I'm always counting at which level a
subproject is relative to the one which depends on it. Moreover, if I decide to move a subproject I have
to update its dependencies with respect to the new location. I think I haveread something in the
documentation but as far as I remember it concerns about library targets.
A nice weekend
Virus checked by G DATA AntiVirusKit
Version: AVK 15.0.960 from 11.11.2004
Virus news: www.antiviruslab.com
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