|
Boost-Build : |
From: Kirill Lapshin (gclbb-jamboost_at_[hidden])
Date: 2003-08-13 07:50:13
John Maddock wrote:
> I'm trying to right a centralised install-like rule using the stage rule,
> but am running into the problem that the stage rule seems to always take the
> path specified as being relative to the current sub-project path, and
> prefixes the path with $(TOP)/$(SUBDIR)/ *even when the path specified is an
> absolute one*. Is there any way around this, and/or is there any variable
> in bjam that points to the project root from the sub-project path (note not
> the same as $(TOP)), so that I could then "undo" the effect that the
> $(TOP)/$(SUBDIR)/ prefix has.
You might want to give path-constant a try.
# Declare and set a project global constant, whose value is a path. The
# path is adjusted to be relative to the invocation directory. The given
# value path is taken to be either absolute, or relative to this project
root.
--Kirill
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