Re: Glib: a Win32 discussion
- From: Kean Johnston <kean johnston gmail com>
- To: Hans Breuer <hans breuer org>
- Cc: gtk-devel-list gnome org
- Subject: Re: Glib: a Win32 discussion
- Date: Sun, 10 Apr 2011 17:06:42 +0200
Agreed, but that is becoming almost impossible to guarantee. If we go to
any lengths to ensure a binary-compiled Glib is linked against msvcrt.dll,
and an average Windows user uses VS2010, they will run into surprises. Even
Microsoft's own code is inconsistent. Some things are now using VS-specific
versions of the CRT while others are using msvcrt.dll. It really is a mess,
and it really is possible to eliminate it from glib. The fact that OTHER
components, such as zlib or libxml2 may be constructed to use crt is ...
frankly ... their issue :) I am trying to address glib. I'll get around to
addressing the same issues in other dependent libraries too but just
becuase zlib may rely on the CRT doesn't mean we shouldn't do what we can
to make glib NOT do so.
But the dependency to the CRT is not the problem, if there is only one of
them in process.
] [Thread Prev