Auto-linking and getting started docs.
I've added a section on auto-linking with MS-Windows compilers in the getting started docs, in the main branch only (No URL yet, cvs hasn't cycled it through yet, but it'll be at http://cvs.sourceforge.net/viewcvs.py/*checkout*/boost/boost/more/getting_st... eventually). If it looks OK, I'll commit to the release branch as well. John.
At 07:51 AM 11/3/2004, John Maddock wrote:
I've added a section on auto-linking with MS-Windows compilers in the getting started docs, in the main branch only
The section you added is informative, but it doesn't directly address the OP's actual problem:
boost-thread correctly looks for boost_thread-bcb-mt-d-1_32.lib, but date_time, filesystem and regex all look for
libboost_XXXXXX-bcb-mt-d-1_32.lib, not boost_XXXXXX-bcb-mt-d-1_32.lib
Isn't this still a problem? --Beman
Beman Dawes wrote:
The section you added is informative, but it doesn't directly address the OP's actual problem:
boost-thread correctly looks for boost_thread-bcb-mt-d-1_32.lib, but date_time, filesystem and regex all look for
libboost_XXXXXX-bcb-mt-d-1_32.lib, not boost_XXXXXX-bcb-mt-d-1_32.lib
Isn't this still a problem?
John's reply to my original post is correct. By default all libraries should use static linking as filesystem did. boost-thread is different as the static lib doesn't work on well on win32 so it always tries to use the dll version. I got confused because: I had to use dynamic RTL because I use boost thread. I thought this meant I had to link against all boost libraries as dlls, but this isn't the case. I can still link against other boost libraries as static libs, providing they are built to use the dynamic rtl (no -s in the file name which indicates use of static rtl). So everything is working as expected. To link against DLLs, I have to define BOOST_ALL_DYN_LINK. The only issue I can see at the moment is that serialization doesn't do auto-linking but Robert as said he doesn't want to play with this before the 1.32.0 release. Thanks Russell
boost-thread correctly looks for boost_thread-bcb-mt-d-1_32.lib, but date_time, filesystem and regex all look for
libboost_XXXXXX-bcb-mt-d-1_32.lib, not boost_XXXXXX-bcb-mt-d-1_32.lib
Isn't this still a problem?
No, the linking against static libs by default was intentional, and discussed a while back, I should add a rationale though. John.
John Maddock writes:
I've added a section on auto-linking with MS-Windows compilers in the getting started docs, in the main branch only (No URL yet, cvs hasn't cycled it through yet, but it'll be at http://cvs.sourceforge.net/viewcvs.py/*checkout*/boost/boost/more/getting_st... eventually). If it looks OK,
It does; thanks for addressing it.
I'll commit to the release branch as well.
Please! -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
John Maddock writes:
I've added a section on auto-linking with MS-Windows compilers in the getting started docs, in the main branch only (No URL yet, cvs hasn't cycled it through yet, but it'll be at http://cvs.sourceforge.net/viewcvs.py/*checkout*/boost/boost/more/getting_st... eventually). If it looks OK,
It does; thanks for addressing it.
It does look good... But it would be nice if you added yourself to the copyright. After all credit, where credit id due ;-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
participants (5)
-
Aleksey Gurtovoy -
Beman Dawes -
John Maddock -
Rene Rivera -
Russell Hind