id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
7163	Issue in glob rule when invoked in <conditional>.	Dmitriy Kinoshenko <dvb.kharkov@…>	Vladimir Prus	"Hi,

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 ] ;
}

project 
    : usage-requirements <include>include ;

lib bar : bar.cpp : <conditional>@print-my-sources ;
<<<

Finally, build from jamroot.jam level and see the output:
My sources:
app.cpp
My sources:
app.cpp

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"".

Attached reworked example/libraries."	Bugs	closed	To Be Determined	build	Boost Development Trunk	Problem	fixed	bjam glob <conditional>