Naming of 32/64 bit libs
Hi, I need both the 32 and 64 bit versions of the boost dll's to coexist in the same directory. Currently when I compile boost, both versions get the same names, e.g. boost_date_time-vc80-mt-1_33_1.dll. Is there any way (apart from modifying boost-base.jam) to change this behaviour, so that the dlls get different names for 32 and 64 bit, such as boost_date_time-vc80_x64-mt-1_33_1.dll for 64 bit? Thanks. -- Anders
awk@imm.dtu.dk wrote:
Is there any way (apart from modifying boost-base.jam) to change this behaviour, so that the dlls get different names for 32 and 64 bit, such as boost_date_time-vc80_x64-mt-1_33_1.dll for 64 bit?
Changing boost-base.jam is the only way :-( But speaking of that... Should we add an architecture tag to the library names? There was also a suggestion on the user list some time ago of adding a user settable build tag so that users could tag individual build+installs. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene Rivera wrote:
But speaking of that... Should we add an architecture tag to the library names? There was also a suggestion on the user list some time ago of adding a user settable build tag so that users could tag individual build+installs.
Both are do-able in the auto-link code (at least I think they are!) Suggestions? Add an archetecture flag in addition to the thread etc tags? We (still) need a way to test this properly BTW. John.
participants (3)
-
awk＠imm.dtu.dk -
John Maddock -
Rene Rivera