Re: [Boost-users] 32- and 64-bit builds on same machine

Subject: Re: [Boost-users] 32- and 64-bit builds on same machine
From: John Dlugosz (JDlugosz_at_[hidden])
Date: 2010-08-16 17:30:37

> > However, this script will not work, because the 32- and 64-bit
> libraries
> > will have the same names and be placed in the same folder, stage/lib.
> >
> > How do I fix that?
> > How do I for instance get the 64-bit libraries in stage/lib(x64)
> instead?
> 
> The first thought that comes to mind is:
> 
> bjam toolset=msvc-9.0 address-model=64 ... stage
> rename stage stage64
> bjam toolset=msvc-9.0 address-model=32 ... stage
> 

I compile and test both 32 and 64-bit builds of a program.  Unlike some final "install" environments where the directories are hidden and transparently forwarded depending on which kind of process is asking, when building and testing it's only sane to have normal files with normal names, and have all files visible to my command shells and other tools.

So, name the files differently!  Have 32- and 64-bit builds produce different names for the DLLs.  Likewise with your programs' exe files (at least for unit tests and tools).

It's also important to match the build options with that of your application.  Several are incompatible.  And for DLLs, you don't want the same named DLL in different places to be different things.  But I've not seen a comprehensive naming convention for Boost for these specific flags (e.g. link against latest CRT or specific version of CRT; iterator debugging; secure library)

--John






TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.