I've just downloaded the latest tarball and have build the DLLs for win32 using bcc32. I rely on auto-link for pick the correct files to link to, and it is looking for libboost_filesystem-bcb-mt-d-1_32.lib but my project is set to use dynamic RTL (because of boost-thread) so shouldn't it link to boost_filesystem-bcb-md-d-1_32.lib? Thanks Russell
Actually, this seems more widespread that just filesystem: My project is set to link to run-time DLLs in C++Builder project options. 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 Shouldn't they pick up the compiler switch that says I'm using runtime-dlls or do I need to explicitly say use boost dlls? Thanks Russell Russell Hind wrote:
I've just downloaded the latest tarball and have build the DLLs for win32 using bcc32.
I rely on auto-link for pick the correct files to link to, and it is looking for libboost_filesystem-bcb-mt-d-1_32.lib but my project is set to use dynamic RTL (because of boost-thread) so shouldn't it link to boost_filesystem-bcb-md-d-1_32.lib?
Thanks
Russell
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
At 06:53 AM 11/2/2004, Russell Hind wrote:
Actually, this seems more widespread that just filesystem:
That was my reaction when I saw your original message. AFAIK, filesystem doesn't do anything different in its handling of autolinking. If it fails under some set of conditions, it is likely that other libraries will fail under those same conditions. --Beman
Actually, this seems more widespread that just filesystem:
My project is set to link to run-time DLLs in C++Builder project options. 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
Shouldn't they pick up the compiler switch that says I'm using runtime-dlls or do I need to explicitly say use boost dlls?
Yes, if you're linking to the dll runtime then you can either link to the static or the dll versions of the libraries. The default is static linking in this release, defining BOOST_ALL_DYN_LINK changes it to dynamic linking. Boost.Threads uses dynamic linking by default because there is no static version, or is there, actually I thought this had been fixed? We also need to add something about this in the getting started docs. John.
John Maddock wrote:
Yes, if you're linking to the dll runtime then you can either link to the static or the dll versions of the libraries.
The default is static linking in this release, defining BOOST_ALL_DYN_LINK changes it to dynamic linking.
Boost.Threads uses dynamic linking by default because there is no static version, or is there, actually I thought this had been fixed?
We also need to add something about this in the getting started docs.
Thanks John, I didn't realise that even though I was using the dynamic runtime, I could still link to static boost libs, providing they were built with the dynamic runtime also. Cheers Russell
participants (3)
-
Beman Dawes -
John Maddock -
Russell Hind