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

[Vinnie Falco via Boost]

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.

[Rene Rivera via Boost]

On Wed, Jun 21, 2017 at 8:50 PM, Vinnie Falco via Boost <

Post by Vinnie Falco via Boost
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.

The change would be here <
https://github.com/boostorg/boost/blob/develop/boostcpp.jam#L111>. Plus
obviously documentation to match the new names. Plus changes to Boost
Config autolinking. Plus documentation for Config autolinking change.

[Gavin Lambert via Boost]

Post by Vinnie Falco via Boost
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


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

[Paul A. Bristow via Boost]

-----Original Message-----
Sent: 22 June 2017 04:54
Cc: Gavin Lambert
Subject: Re: [boost] [build] Use address-model in library filenames

Post by Vinnie Falco via Boost
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.

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]






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

[Olaf van der Spek via Boost]

On Thu, Jun 22, 2017 at 11:04 AM, Paul A. Bristow via Boost

Post by Paul A. Bristow via Boost
(What is this 'stage' stuff anyway - that never gets installed? Pure obfuscation?)

On Windows I put the stage dir in the lib path.. what does install do
on Windows?

Post by Paul A. Bristow via Boost
We don't have the people resource?

There's definitely a problem with people resources.