Re: How to suppress toolset in target paths?

From: David Abrahams (dave_at_[hidden])
Date: 2004-12-10 11:39:30

Vladimir Prus wrote:
> On Thursday 09 December 2004 20:21, David Abrahams wrote:
>> I didn't notice this before, but now I am seeing C++ toolsets showing up
>> as relevant features in my documentation builds:
>>
>> MkDir1 libs\numeric\mtl\doc\bin
>> MkDir1 libs\numeric\mtl\doc\bin\gcc-3.2
>> MkDir1 libs\numeric\mtl\doc\bin\gcc-3.2\debug
>> docutils.html libs\numeric\mtl\doc\bin\gcc-3.2\debug\plan.html
>> docutils.html libs\numeric\mtl\doc\bin\gcc-3.2\debug\sow.html
>>
>> What have I done wrong?
> 
> Nothing, it's the only behaviour currently. Now, there are two approaches how 
> to deal with it.
> 
> 1. The <in-path> feature we've discussed previously, that should control which 
> properties how up in path and which don't. Problem: it must be set on each 
> target.

Having a terrible time finding any docs for that feature or even the
discussion history. Can you help? My main concern is that we should be
able to say "not-in-path."

> 2. Allow to specify, when declaring *generator*, the list of relevant 
> properties. When creating targets, only relevant properies will be left in 
> property-set.
> 
> The second approach is nice because everywhere you write:
> 
> html a : a.rst ;
> 
> you'll have 'a.html' just in "bin". You don't need any explicit <in-path>. I 
> attach a patch which implements this idea. With that patch, I get:
> 
> 
> docutils.html bin/a.html
> 
> PYTHONPATH=foo:foo/extras;export PYTHONPATH
> python foo/tools/rst2html.py a.rst bin/a.html
> 
> Comments are most welcome!

I'm sorry, I'm confused about why anything explicit should have to be
said about which properties are relevant. In BBv1 the flags rule took
care of making properties relevant. You might only need to augment that
information in a few rare cases.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com