[config] Why don't 32-bit and 64-bit Windows DLL's have different names?
A C++ committee library working group member just asked me why Boost 32-bit and 64-bit Windows DLL's don't have different names. I couldn't remember; could someone please explain? --Beman PS: http://www.boost.org/development/separate_compilation.html is looking a bit dated due to the references to older VC++ versions. Perhaps someone could do a pass through it adding more modern references.
Beman Dawes wrote:
A C++ committee library working group member just asked me why Boost 32-bit and 64-bit Windows DLL's don't have different names.
I couldn't remember; could someone please explain?
Beman, I suppose the answer is that: (i) back then when the scheme was settled, 64-bit Windows was rare (ii) folks often switch between debug/release builds so that's encoded in name. folks much less often switch between 32 and 64 bits, on the same machine. HTH, Volodya -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40
This is actually one of my personal 'pet peeves'. Can we please add an option to 'fix' this? It makes deploying Boost with your application more difficult than it otherwise needs to be... I'm happy to take the time to throw together a patch if need be, but I figure it's a relatively trivial fix for somebody more experienced with BBv2. On Thu, Mar 31, 2011 at 1:21 AM, Vladimir Prus <vladimir@codesourcery.com>wrote:
Beman Dawes wrote:
A C++ committee library working group member just asked me why Boost 32-bit and 64-bit Windows DLL's don't have different names.
I couldn't remember; could someone please explain?
Beman,
I suppose the answer is that:
(i) back then when the scheme was settled, 64-bit Windows was rare (ii) folks often switch between debug/release builds so that's encoded in name. folks much less often switch between 32 and 64 bits, on the same machine.
HTH, Volodya
-- Vladimir Prus Mentor Graphics +7 (812) 677-68-40
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Joshua Boyce wrote:
This is actually one of my personal 'pet peeves'. Can we please add an option to 'fix' this? It makes deploying Boost with your application more difficult than it otherwise needs to be...
I'm happy to take the time to throw together a patch if need be, but I figure it's a relatively trivial fix for somebody more experienced with BBv2.
Well, you need to also modify autolink code, and documentation. Also, the fact that Boost.Build change is trivial makes it very suitable for somebody not very experienced with it ;-) - Volodya -- Vladimir Prus Mentor Graphics +7 (812) 677-68-40
participants (3)
-
Beman Dawes -
Joshua Boyce -
Vladimir Prus