Paul Pluzhnikov wrote:
> Chuck Dillon <spam@nimblegen.com> writes:
>
> <snip>
> 
>
>
> I understand what you are referring to, but I think you don't have
> much (recent) experience with Windows DLLs.

Actually, I only have fairly recent experience.  I don't have much
historic experience nor knowledge of Winders SDK internals so some of
my efforts to elaborate were inaccurate.  My primary point revolves
around the C-runtime implementations in the Winders world and the
various complexities it can introduce.  Those complexities are directly
related to sharing information across/between the libCRT ABIs.  Perhaps
it is inaccurate to extrapolate the seemingly assinine limitations of
the CRT implementations to the architecture of DLLs.

>
> To build a DLL that would function pretty close to a UNIX DSO (at
> least WRT malloc) all you have to do is compile and link everything
> with /MD switch.

Again, *pretty close* is a lot of the point I was trying to make.  It
is over-simplifying things to suggest just link /MD.  When 3rd party
DLLs are involved compatible links might not be possible or might
require special builds from the vendor if they will provide them.  They
might just say: "What do you mean you're not building an MFC app?" If
you need the C-Runtimes (CRT) DLLs you can run into conflicts just
mixing MS technologies.

>
> 
>
>
> Not if you compiled everything with /MD.

Like I said, that is easy to say but not always doable.  It's a
most-of-the-time solution.

-- ced


--
Chuck Dillon
Senior Software Engineer
NimbleGen Systems Inc.

[ Post a follow-up to this message ]