[Boost] Is this library availble for 64 bit?
Jaiswal, Usha [OS-IE] escribió:
Is there any version of Boost for 64 bit.
Hello, Most libraries are currently running in several 64-bit environments without problems; take a look at http://www.boost.org/development/tests/trunk/developer/summary.html which includes several 64-bit platforms. In principle you don't have to do any special to work in such an environment: simply include header-ony libs as always or build the libs that need to be built following the instructions at: http://www.boost.org/more/getting_started/index.html Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Hi All, Can anyone tell me the steps to build boost_1_34_1 for 64 bit platform..?? Configuration I am using is: OS: Windows XP professional x64 Edition Processor: AMD Athlon(tm) 64 Processor And I am using visual studio 2005. I got steps to build boost_1_33_1 at site http://en.allexperts.com/q/C-1040/Building-boost-libraries-64.htm And tried to use same steps to build boost_1_34_1 for 64 bit platform but python library was not built and thread library was also not built and there were some other issues also. Thanks a lot.. Usha Jaiswal.
Jaiswal, Usha [OS-IE] wrote on Friday, May 29, 2009 1:27 AM:
Can anyone tell me the steps to build boost_1_34_1 for 64 bit platform..??
Configuration I am using is: OS: Windows XP professional x64 Edition Processor: AMD Athlon(tm) 64 Processor
And I am using visual studio 2005.
I got steps to build boost_1_33_1 at site http://en.allexperts.com/q/C-1040/Building-boost-libraries-64.htm
And tried to use same steps to build boost_1_34_1 for 64 bit platform but python library was not built and thread library was also not built and there were some other issues also.
I had to build Boost 1.34.1 for Win64, VS 2005 a couple weeks ago. I unpacked the Boost tarball and ran the following bjam command line: bjam --prefix=C:\Boost64 --build-dir=D:\boost-build\x64 --toolset=msvc address-model=64 install I verified that thread libraries were built, but I haven't tested them. Also, I am not using Python, but it should be the same procedure as Python for Win32. This is basically the same bjam command as for 32-bit compilation. The important differences are: address-model=64 Requests a 64-bit build --prefix=C:\Boost64 Do NOT put your 64-bit Boost in the same directory as your 32-bit Boost. You'll overwrite the libraries. --build-dir=D:\boost-build\x64 The same holds true for the indermediate files. This should point to an empty directory. HTH Andrew Holden
It will be a while before I can attempt to build boost or boost x64, but I wanted to know how it names or deposits the 64 bit binaries? Should I expect '64' embedded in the ABI tags like the following? * boost_tetris-vc90-mt-1_40.dll //32 bit release * boost_tetris-vc90-mt-d-1_40.dll //32 bit debug * boost_tetris-vc90-mt-64-1_40.dll //64 bit release * boost_tetris-vc90-mt-d64-1_40.dll //64 bit debug ...Or should I expect that 32 bit binaries will show up in a "lib" folder, and 64 bit binaries will have the same names and show up in a "lib_64" folder? Part of what makes this question interesting is how Windows locates and loads 32/64 bit DLLs. If a 32 bit process tries to load a boost library, but encounters a 64 bit version of the library, it will silently skip past the 64 bit version until it locates the 32 bit version in some other path. The opposite is also true (if seeking 64 bit, it will silently skip any 32 bit it finds so that it locates the 64 bit version on another path). It is debatable whether that behavior should be exploited by developers and vendors, but the behavior is lost if the 32/64 boost binaries have different names. How does the community feel about this? Should those values ('32' or '64') be embedded in the name? Which direction is boost heading on this matter? -Brent
On Wed, Feb 10, 2010 at 07:05:54PM -0700, Brent Arias wrote:
It will be a while before I can attempt to build boost or boost x64, but I wanted to know how it names or deposits the 64 bit binaries? Should I expect '64' embedded in the ABI tags like the following? ...Or should I expect that 32 bit binaries will show up in a "lib" folder, and 64 bit binaries will have the same names and show up in a "lib_64" folder?
None of the above. The library names and output folders are sadly identical when building with address-model=32 vs. address-model=64. I would be rather happy if a change towards adding an arch/OS tag happened, as currently I must manually separate libraries for different OSes and architectures. There would be a need for some additional cleverness in the auto-link bits of Boost.Config, but hopefully nothing horribly major. Most of the work would be in BoostBuild I reckon. -- Lars Viklund | zao@acc.umu.se
participants (1)
-
Andrew Holden -
Brent Arias -
Jaiswal, Usha [OS-IE] -
joaquin＠tid.es -
Lars Viklund