Re: [Boost-build] intermediate directory control

Subject: Re: [Boost-build] intermediate directory control
From: Nogradi, Chris (Chris.Nogradi_at_[hidden])
Date: 2012-05-15 12:23:36

> On Tuesday, May 15, 2012 9:33 AM, George Georgiev wrote:
> > On Mon, May 14, 2012 at 6:02 AM, Nogradi, Chris wrote:
> > Would it be possible to also provide a version of abbreviate-paths
> > that is guaranteed to not go beyond the windows path limit?
>
> My 2 cents.
>
> I have some concerns about this idea.
>
> The abbreviated path will be function of the root directory and the
> max length of the file targets. This means that running the build from
> different root directory could change the location path.

Hmm I double checked our builds and all commands to compiler/linker/tools are relative to the root.
So I don't think the root dir would be a function of the algorithm unless you are explicitly doing something to override this default behavior.

Which makes me wonder why in Jenkins you are seeing an issue.

I use matrix builds also and yes the root depth increases but the commands to the tools stay the same.

> Even adding a new target with longer name could change it.
>

Good point.  However, if you add a new target and the paths blows up then you have to change the environment anyways to deal with the problem.  At least, with this feature, only the targets in the same destination path would be relocated and rebuilt rather than the whole project.

> I think the persistence of the location path is important.

Yes that would be ideal and maybe even sufficient reason to abandon this request.

Thanks for your 2c

Chris

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.

Thank you for your cooperation.