[glib: 6/13] docs: Drop outdated cross-building documentation from README.win32
- From: Philip Withnall <pwithnall src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib: 6/13] docs: Drop outdated cross-building documentation from README.win32
- Date: Tue, 15 Jan 2019 15:27:09 +0000 (UTC)
commit 64bd539d155990e22d0bbe1689f253c4a808e47e
Author: Philip Withnall <withnall endlessm com>
Date: Wed Jan 9 11:40:46 2019 +0000
docs: Drop outdated cross-building documentation from README.win32
It is very very outdated and irrelevant now.
Signed-off-by: Philip Withnall <withnall endlessm com>
README.win32 | 56 --------------------------------------------------------
1 file changed, 56 deletions(-)
---
diff --git a/README.win32 b/README.win32
index 6933e6690..b7bce104b 100644
--- a/README.win32
+++ b/README.win32
@@ -5,9 +5,6 @@ Note that this document is not really maintained in a serious
fashion. Lots of information here might be misleading or outdated. You
have been warned.
-The general parts, and the section about gcc and autoconfiscated
-build, and about a Visual Studio build are by Tor Lillqvist.
-
General
=======
@@ -117,59 +114,6 @@ Before building GLib you must also have a GNU gettext-runtime
developer package. Get prebuilt binaries of gettext-runtime from
http://www.gtk.org/download-windows.html .
-Autoconfiscated build (with gcc)
-================================
-
-Tor uses gcc 3.4.5 and the rest of the mingw utilities, including MSYS
-from www.mingw.org. Somewhat earlier or later versions of gcc
-presumably also work fine.
-
-Using Cygwin's gcc with the -mno-cygwin switch is not recommended. In
-theory it should work, but Tor hasn't tested that lately. It can
-easily lead to confusing situations where one mixes headers for Cygwin
-from /usr/include with the headers for native software one really
-should use. Ditto for libraries.
-
-If you want to use mingw's gcc, install gcc, win32api, binutils and
-MSYS from www.mingw.org.
-
-Tor invokes configure using:
-
-CC='gcc -mtune=pentium3 -mthreads' CPPFLAGS='-I/opt/gnu/include' \
- LDFLAGS='-L/opt/gnu/lib -Wl,--enable-auto-image-base' CFLAGS=-O2 \
- ./configure --disable-gtk-doc --prefix=$TARGET
-
-The /opt/gnu mentioned contains the header files for GNU and (import)
-libraries for GNU libintl. The build scripts used to produce the
-prebuilt binaries are included in the "dev" packages.
-
-Please note that the ./configure mechanism should not blindly be used
-to build a GLib to be distributed to other developers because it
-produces a compiler-dependent glibconfig.h.
-
-Except for this and a few other minor issues, there shouldn't be any
-reason to distribute separate GLib headers and DLLs for gcc and MSVC6
-users, as the compilers generate code that uses the same C runtime
-library.
-
-The DLL generated by either compiler is binary compatible with the
-other one. Thus one either has to manually edit glibconfig.h
-afterwards.
-
-For MSVC7 and later (Visual C++ .NET 2003, Visual C++ 2005, Visual C++
-2008 etc) it is preferred to use specific builds of GLib DLLs that use
-the same C runtime as the code that uses GLib.
-
-For GLib, the DLL that uses msvcrt.dll is called libglib-2.0-0.dll,
-and the import libraries libglib-2.0.dll.a and glib-2.0.lib. Note that
-the "2.0" is part of the "basename" of the library, it is not
-something that libtool has added. The -0 suffix is added by libtool
-and is the value of "LT_CURRENT - LT_AGE". The 0 should *not* be
-thought to be part of the version number of GLib. The LT_CURRENT -
-LT_AGE value will on purpose be kept as zero as long as binary
-compatibility is maintained. For the gory details, see configure.ac
-and libtool documentation.
-
Building with Visual Studio
===========================
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]