Re: [Boost-Users] building threads lib with latest from CVS
From: "hunleyexpress <mhunley@pocketpurchase.com>" <mhunley@pocketpurchase.com> Date: 2003/02/10 Mon PM 02:07:11 EST To: Boost-Users@yahoogroups.com Subject: [Boost-Users] building threads lib with latest from CVS
I am fairly new to boost (and jamfiles). I am using the threads library for cross platform thread support. Under the stable build a library libboost_thread.lib is created to staticly link in to my project, with seperate libs if I am using the DLL STL or static STL.
That build config is gone in the latest version under CVS, replaced by a boost_thread dll set up. I want (and need) the old static version. I have successfully added it back into the jam file so that all 3 (including the threadmon) are built now, but that isn't something I really want to have to maintain as I get updates. Is the static lib intentionally and permanently removed or is it an oversight/temporary change?
Intentionally removed. In the current library it's easier to deal with a single build type, and since a DLL is required for TLS usage, the static build was removed. In the next version of the library, the implementation is going to have to make use of TLS as well, so you'll always need a DLL, making it pointless to continue providing both a static library and the threadmon.dll. William E. Kempf wekempf@cox.net
Intentionally removed. In the current library it's easier to deal with a single build type, and since a DLL is required for TLS usage, the static build was removed. In the next version of the library, the implementation is going to have to make use of TLS as well, so you'll always need a DLL, making it pointless to continue providing both a static library and the threadmon.dll.
If you mean something other than Transport Layer Security when you say TLS, disregard the rest of this and just let me know what it means in boost-ese. I don't quite understand why the threading lib depends on TLS. I am only including the threading lib to write thread handling and don't want or need security aspects (I'm handling those specifically myself for a custom app). I ultimately need to bundle all of it into a *very* small DLL (or shared lib on Linux) of my own and don't want to require a separate boost DLL. Why would you tie the two together, they seem completely orthoganal. BTW: I have found it rather easy to have Jam build both. I guess it is just more headache from a testing standpoint. I appreciate the info.
participants (4)
-
hunleyexpress <mhunleyï¼ pocketpurchase.com> -
William E. Kempf