Subject: [Boost-build] Issue in glob rule when invoked in <conditional>.
From: dimak (dvb.kharkov_at_[hidden])
Date: 2012-07-23 16:49:26
I am replicating here the issue definition I posted at Boost track tickets,
*Ticket #7163* (https://svn.boost.org/trac/boost/ticket/7163) attached with
issue appearance example.
*Description of the bug:*
When we use glob rule inside conditional in dependency target, it makes
"globbing" not inside directory of dependency project, but inside
dependent one. To reproduce, take example/libraries from boost build
repository, amend util/foo/jamfile to introduce <conditional>:
rule print-my-sources ( properties * )
ECHO My sources: ;
ECHO [ glob *.cpp ] ;
: usage-requirements <include>include ;
lib bar : bar.cpp : <conditional>@print-my-sources ;
Finally, build from jamroot.jam level and see the output:
We expected to see "bar.cpp", while it seems that context was not switched
from dependent "app" to dependency "util/foo", and thus we got "app.cpp".
-- View this message in context: http://boost.2283326.n4.nabble.com/Issue-in-glob-rule-when-invoked-in-conditional-tp4633477.html Sent from the Boost - Build mailing list archive at Nabble.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