summaryrefslogtreecommitdiff
path: root/README.win32
diff options
context:
space:
mode:
authorTor Lillqvist <tml@src.gnome.org>1999-03-25 22:55:48 +0000
committerTor Lillqvist <tml@src.gnome.org>1999-03-25 22:55:48 +0000
commitaa8d510e87a2c4e496a9f812e2617ba1619a2517 (patch)
tree5e11164df4e5c3b7a7ad05bd242b9a4db40ca99e /README.win32
parent79986f1e8b29fe9a1558c3264a8ce195c3e3f748 (diff)
downloadglib-aa8d510e87a2c4e496a9f812e2617ba1619a2517.tar.gz
Update version numbers.
* config.h.win32: Update version numbers. * glibconfig.h.win32: Update version numbers and pthreads-win32- related magic values. * README.win32: Some improvements. * makefile.msc: Add gqueue and gstack. Correct version number.
Diffstat (limited to 'README.win32')
-rw-r--r--README.win3213
1 files changed, 7 insertions, 6 deletions
diff --git a/README.win32 b/README.win32
index 27c4b7fe0..4d4e023fe 100644
--- a/README.win32
+++ b/README.win32
@@ -6,11 +6,12 @@ by the Microsoft runtime C library. Additionally the pthreads
emulation library is used.
As for now, to build GLib on Win32, you need the Microsoft compiler
-and tools. Both the compiler from MSVC 5.0 and MSVC 6.0 have been used
-successfully.
+and tools. Both the compiler from MSVC 5.0 and from MSVC 6.0 have been
+used successfully.
Before building you must get the pthreads library for Windows from
-http://sourceware.cygnus.com/pthreads-win32/. Edit the location of the
+http://sourceware.cygnus.com/pthreads-win32/. The pthreads-win32
+snapshot from 1999-03-16 is mostly OK. Edit the location of the
pthreads library and include files in makefile.msc. Also edit the BIN
definition in makefile.msc.
@@ -44,11 +45,11 @@ related to Win32:
- _MSC_VER is defined when using the Microsoft compiler.
Currently the Win32 port uses the combination with all three of those
-on, but eventually the cygwin compiler and tools will be supported
-also, and in that case _MSC_VER wouldn't be defined.
+on, but eventually "gcc -mno-cygwin" will be supported also, and in
+that case _MSC_VER wouldn't be defined.
Some of the usage of these macros is probably a bit mixed up, and will
have to be straightened out when actually trying other combinations.
The pthreads for Win32 package that the thread support uses isn't
-released yet, and thus threads really should not be relied upon.
+quite ready yet, and thus threads really should not be relied upon.