I&#39;m using VS2005 to compile a DLL that links with the MFC DLL and also the static Boost threads library. I&#39;ve upgraded from Boost v1.34.1 to v1.37 and now the threads library&#39;s use of MSCRT&#39;s _pRawDllMain hook interferes with MFC&#39;s use of the hook to point to its _RawDllMain export. I&#39;ve come up with a workaround of a library that exports _pRawDllMain and links to _RawDllMain in the MFC DLL and an export I&#39;ve added to the threads library that calls its dll_callback() function. I just can&#39;t get the MS linker to cooperate.<br>
<br>If I put my library ahead of the threads library in the command line the linker complains of a multiply-defined symbol. If I put the threads library ahead of my library the linker uses the threads library _pRawDllMain export and ignores mine. Only if I remove the _pRawDllMain export from the threads library entirely does the linker use mine. I would like to leave the _pRawDllMain export in the threads library so that it will still work in my library&#39;s absence but I can&#39;t figure out what makes it so attractive to the linker.<br>
<br>I realize this isn&#39;t, strictly speaking, a Boost issue, but the problem arose because of a change to Boost and I know there are a lot of smart people here. :)&gt;<br><br>-evan<br>