RE: RE: [xml] wrong compiler settings for MSVC in makefile

[Jesse Pelton <jsp PKC com>]

Yeah, that's the message I referred to as well.  I wasn't proposing to add a
#define, though, just pointing out that LIBXML_STATIC_FOR_DLL had no effect
when TLS is used.

Do we need documentation of the various #defines: what does each do, how do
they interact?  I hesitate to bring it up, because I'm not volunteering, at
least not right now.  This could be a substantial project, and I'm not sure
where the resulting document would belong.  To be manageable, it probably
should be restricted to Windows-specific constants, since that's where much
of the bizarre ugliness lies.

> -----Original Message-----
> From: oliverst online de [mailto:oliverst online de] 
> Sent: Tuesday, November 18, 2003 9:50 AM
> To: Jesse Pelton
> Cc: Ed Day; Igor Zlatkovic; xml gnome org
> Subject: Re: RE: [xml] wrong compiler settings for MSVC in makefile
>
>
>
> I am reffering to your own post:
http://mail.gnome.org/archives/xml/2003-October/msg00165.html

And I just saw, that Ed also mentioned those -ML/-MT/-MD stuff back
there, too.

Jesse Pelton <jsp PKC com> schrieb am 18.11.2003, 15:27:33:
> I don't have any recollection of another #define being discussed, and I
> can't find it in the archives.  (There is at least one message about TLS
> issues, though.)  Oliver, can you look for the relevant discussion, in
case
> something important got missed?
>
> > -----Original Message-----
> > From: Oliver Stöneberg [mailto:oliverst online de] 
> > Sent: Monday, November 17, 2003 4:36 PM
> > To: Ed Day; Igor Zlatkovic; xml gnome org
> > Subject: Re: [xml] wrong compiler settings for MSVC in makefile
>
> > I am not sure, if there was an exception in case of "tls" set for 
> > threads. You have to look-up some discussion around the beta6 time on 
> > the list. I had a lot of problems with the lib linked statically to 
> > DLLs in that time and before that. Somebody wanted to add that 
> > special define at least for documentation reason (was it you, Igor?). 
> > But hasn't done it yet.