Boost logo

Boost-Build :

Subject: Re: [Boost-build] intermediate directory control
From: Vladimir Prus (ghost_at_[hidden])
Date: 2012-05-13 02:19:18

On 13/05/12 05:29, Steven Watanabe wrote:
> On 05/12/2012 06:07 PM, George Georgiev wrote:
>> Is it possible I to supply my own hash function for the --hash option?
>> MD5 is OK for the CI, but I wish it is a little bit more human
>> friendly when I need to browse intermediate directory.
> It isn't possible now, but it sounds like a great
> idea to me. This issue comes up pretty often here.
> How does something like this look:
> project : requirements<location-property-path>@compute-property-path ;
> rule compute-property-path ( property-set )
> {
> local p = [ $(property-set).as-path ] ;
> # change p
> return $(p) ;
> }
> This would also allow you to include/exclude
> any properties you want.
> Volodya? If this seems reasonable I'll
> start implementing it. It should be
> pretty straightforward. (Obviously
> the property could use a better name.
> location-property-path is just the
> first thing that came to mind)


this makes sense to me. I am somewhat worried about adding the number of solutions though. Maybe,
we should declare --abbraviate-paths as deprecated when you implement your proposal? Or maybe,
we should eventually extend '--hash' to generate some kind of manifest file explaining where
to find which build products?


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at