...by allowing our special @___... tokens anywhere within an install name,
so that external modules can configure --prefix=/@___... etc. This removes
the need for the special extshl and EXTRPATH=LOADER. Also, a new
OUT2BIN_NONE can be used for external modules where the generated libraries
need the default EXTRPATH=OOO, but generated executables are only used
during the build and such need RPATH=NONE.
o test.mo ./de.po; \
../.././install-sh -c -d de/LC_MESSAGES; \
cp -f test.mo de/LC_MESSAGES
/bin/sh: line 1: o: command not found
cp: test.mo: No such file or directory
make[5]: [test.mo] Error 1 (ignored)
Patch out the chunk of GLib's configure script that looks for
libintl. Take care of fallout in a couple of places in GLib
sources. The end result is that GLib doesn't use any libintl (gettext
etc) functionality. Which is nice, as we then shouldn't need to build
gettext. No functionality should be lost, as we weren't delivering any
GLib message catalogs anyway, so none of the gettext calls at least
here would ever have found any localised messages.
Pass --build and --host options to the configure script. Pass a bunch
of a priori cached test results for stuff that can't be determined
when cross-compiling. Link with the CoreFoundation framework. Build
static archives.
Patch out the compile-time USE_LIBICONV_GNU and _LIBICONV_H test from
gconvert.c as it for some reason fails for iOS.
Don't use the same name for the GLib DLLs that we build with MSVS9 as
in the "official" MinGW-built packages (either the ones from
www.gtk.org, or the ones from OBS). The "official" GLib DLLs use
msvcrt.dll, while the ones we build use msvcr90.dll. We want to avoid
potential confusion. Call the DLLs we build glib-2.0.dll etc, not
libglib-2.0-0.dll etc.
