path.glob-tree

Rene,
I see that you've added path.glob-tree function, that more
than one user has 
asked about. Thanks!

Do you think we should also added rule 'glob-tree' callable
in project's 
context, just like we have 'glob' rule? 

The explain, the difference between path.glob and glob are
that:

   1. glob searches relatively from the project where it's
used. It's much
   easier than getting the path to current Jamfile and
passing that
   to path.glob.

   2. The result has relative paths from the project's
source dir -- 
   so result of glob can be directly passed to any main
target.

   For example, if you use path.glob in
$project_root/foo/bar, then
   path.glob will likely return paths like
"foo/bar/whatever", and if
   you try to use such paths in foo/bar/Jamfile, it will
fail. The 'glob'
   rule will strip the "foo/bar" prefix.

The new 'glob-tree' would do the same extra processing that
'glob' does. The 
change itself it straightforward, I can do it. I was just
checking that it 
would be fine with you.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:
> The new 'glob-tree' would do the same extra processing
that 'glob' does. The 
> change itself it straightforward, I can do it. I was
just checking that it 
> would be fine with you.

Sure that's fine.

You might want to call the ".glob-tree" version,
and hence make it 
non-local, to save on redoing some of the path translations.


-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software
.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build