Re: New release of GTK+ libraries (1.3.12)
- From: Tor Lillqvist <tml iki fi>
- To: gtk-devel-list gnome org
- Cc: "Gerrit P. Haase" <gp familiehaase de>
- Subject: Re: New release of GTK+ libraries (1.3.12)
- Date: Mon, 7 Jan 2002 01:22:16 +0200 (FLE Standard Time)
Gerrit P. Haase writes:
> These are not needed on/with Cygwin (cygwin1.dll is a posix-layer and
> substitutes all needs to link against windows libs).
Well, that depends on how you look at it. There are some things that
you still really want to use from the Windows libraries, even on
Cygwin.
One example is i18n stuff. If you want to have working
g_locale_{to,from}_utf8() functions, you need to use
MultiByteToWideChar() or WideCharToMultiByte() to convert from the
character set used for file names (and visible also to Cygwin programs
through Cygwin's readdir() AFAIK) to UTF-8 and vice versa. Of course,
you could just ignore these issues, and pretend good old ASCII is good
for everybody ;-)
The preprocessor macro G_PLATFORM_WIN32 is supposed to be defined both
on plain Win32 ("mingw") and Cygwin, and those places in GLib which
are supposed to be built both for mingw and Cygwin are #ifdeffed with
that. There might well be glitches in where this is used, however,
there hasn't been that much feedback from people building GLib on
Cygwin.
> It compiles without these libs, no problems after I removed them
That probably is because the Cygwin gcc always links with them anyway,
or at least with -lkernel32? (Try gcc -v.) Or how did it otherwise
satisfy for instance the MultiByteToWideChar references from
gconvert.o?
> Besides this little `bug' it builds OOTB;)
But how well does "make check" work?
--tml
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]