Re: [boost] [build] Use address-model in library filenames

Subject: Re: [boost] [build] Use address-model in library filenames
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2017-06-22 09:04:33

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Gavin Lambert via Boost
> Sent: 22 June 2017 04:54
> To: boost_at_[hidden]
> Cc: Gavin Lambert
> Subject: Re: [boost] [build] Use address-model in library filenames
> 
> On 22/06/2017 13:50, Vinnie Falco wrote:
> > Please add the address-model (32 or 64) into the encoded name which
> > describes a library, so that 32-bit and 64-bit libraries may reside in
> > the same dir.
> >
> > I'd like to avoid a lengthy debate, and if no one wants to do it just
> > provide me with working code for accomplishing it and I'll submit a
> > pull request.
> 
> If you want to do it for local builds without modifying Boost itself, see:
> 
>    https://stackoverflow.com/a/42408982/43534

Or you can split into two folders, perhaps called lib/win32 and /x64 - works for me, and others.

(What is this 'stage' stuff anyway - that never gets installed?  Pure obfuscation?)

But surely it would be much better to continue to add the address variant to the library filename as with other variants.

We discussed this years ago and nobody has felt able to make it happen.

Isn't this a warning about making any grand changes like cmake?

We don't have the people resource?

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]