Added win32-specific --export-all-symbols to linker flags. This is

2004-01-27  Cedric Gustin  <cedric.gustin@swing.be>

	* build_shared/Makefile_build.am_fragment: Added win32-specific
	--export-all-symbols to linker flags. This is backported from
	gtkmm-2.2.
	* README.win32: Updated text for glibmm-2.4.
	* tools/generate_wrap_init.pl.in: Replaced GTKMM_WIN32 by the
	standard G_OS_WIN32.

1 files changed, 11 insertions, 34 deletions

diff --git a/README.win32 b/README.win32
index 891ca803..e015b43b 100644
--- a/README.win32
+++ b/README.win32
@@ -1,11 +1,11 @@
-Building gtkmm on Win32
+Building glibmm on Win32
 ===========================
 
 Currently, only the mingw (native win32) gcc compiler is supported
 through the gnu autotools (automake, autoconf, libtool). As explicitly
 stated in the gtk+ for win32 distribution (http://www.gimp.org/win32/),
 the gcc compiler provided by the cygwin distribution should not be
-used to build gtk+/gtkmm libraries and/or applications (see the
+used to build glib/glibmm libraries and/or applications (see the
 README.win32 that comes with the gtk+ DLLs). This MIGHT cause
 conflicts between the cygwin and msvcrt runtime environments.
 
@@ -26,11 +26,11 @@ that were mentioned above) with mingw by making sure that the mingw
 tools (gcc, ld, dlltool, ..) are called first.
 
 First, make sure that you have working distribution of the native port
-of both libsigc++-1.2.x and gtk+-2.0 on win32 (see
-http://www.gimp.org/win32). If you can't compile a simple gtk+ example
+of both libsigc++-1.2.x and glib-2.0 on win32 (see
+http://www.gimp.org/win32). If you can't compile a simple glib example
 using gcc and `pkg-config --cflags --libs`, you should not even think
-about trying to compile gtkmm, let alone using precompiled libgtkmm
-DLLs to port your gtkmm application !
+about trying to compile glibmm, let alone using precompiled libglibmm
+DLLs to port your glibmm application !
 
 The configure script can then be called using (as an example) the
 following options
@@ -47,9 +47,9 @@ Because Dll support with libtool on the mingw32 platform is fairly recent, it
 requires developement version of autoconf/automake and libtool, as provided by
 the autotools-devel package in the cygwin distribution. Currently, this means
 
-libtool : 1.4e
-automake : 1.7.2
-autoconf : 2.57
+libtool : 1.5
+automake : 1.7.9
+autoconf : 2.59
 
 IMPORTANT WARNING : the libtool scripts contained in the source distribution
 of the library might not be recent enough to support dll creation. It will 
@@ -79,30 +79,7 @@ before running the configure script again.
 In the future, a specially tuned source distribution along with a binary 
 package might be provided for mingw.
 
-2. Other compilers (MSVC, borland)
+2. Glibmm methods and signals not available on win32
 
-While some compiler options are present in the configuration files,
-other compilers are currently not supported, but everyone is free to give it 
-a try ! 
-
-3. Gtkmm methods and signals not available on win32
-
-Although is the win32 port of gtk+-2 is rapidly catching up with it
-unix counterpart, some gtkmm methods and signals are still missing on
-win32. These are
-
-* Implemented in the C library but not DLL exported
-
-Atkmm :
-	Action::get_localized_name
-	Component::get_layer
-	Component::get_mdi_zorder
-	Object::add_relationship
-	Object::remove_relationship
-
-* Not Implemented in the C library
-
-Gtkmm :
-	Gtk::Plug (not available on win32)
-	Gtk::Socket (not available on win32)
+All glibmm methods and signals are available on win32.