There are traps in the MS world. Some CRT functions (think strtok - yuk) use static data. If you build with the statically linked version of the library, each executable (.exe AND .dll) has it's own copy of that static data and they don't know about each other. All executables built with the dynamically linked version share the same copy of that static data. If you use the dynamically linked version then you should (on Win NT and up systems - not Win 9x) share the same copy of the code with all other apps in the system that use the CRT. HTH - Richard -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Roland Schwarz Sent: 25 November 2004 10:45 To: boost-users@lists.boost.org Subject: Re: [Boost-users] Re: Memory leak reported using threads library I inadvertently replied to the wrong posting. John Maddock wrote:
That's your problem: there must be one single rtl shared both by your code and the Boost.Threads dll: and that means using the dynamic C runtime.
That surprises me somewhat. Explicitely: mydll depending on dynamic CRT. myapp depending on static CRT and depending on mydll. You think this is not possible? Just tried it. Found no obvious problem. Are there hidden traps? If this would not be possible you never could write a self contained dll ! But I think I didn't understand your argument corectly, could you elaborate please? Hmm, when I rethink the issue the following might happen: Writing a app that uses static CRT, then requesting for the DLL version of a boost lib. Could it be that the autolink feature pulls in dll versions of CRT? If this is the case this points out a problem with the autolink, and has nothing to do with the unfeasability of the above scenario. Roland _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.797 / Virus Database: 541 - Release Date: 15/11/2004 --- Outgoing mail is Virus checked. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.797 / Virus Database: 541 - Release Date: 15/11/2004