[build] Use address-model in library filenames
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. -- Follow me on Github: https://github.com/vinniefalco
On Wed, Jun 21, 2017 at 8:50 PM, Vinnie Falco via Boost < boost@lists.boost.org> 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.
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. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
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
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Gavin Lambert via Boost Sent: 22 June 2017 04:54 To: boost@lists.boost.org 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:
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 +44 (0) 1539 561830
On Thu, Jun 22, 2017 at 11:04 AM, 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?
We don't have the people resource?
There's definitely a problem with people resources. -- Olaf
participants (5)
-
Gavin Lambert -
Olaf van der Spek -
Paul A. Bristow -
Rene Rivera -
Vinnie Falco