reorganize the sample splitting it in two source files and an additional header;...

[wxWidgets.git] / docs / x11 / install.txt

diff --git a/docs/x11/install.txt b/docs/x11/install.txt
index b4b3083f46b02e2dd11a91c9a38ec0f48cf26ea8..d9d78aabe3a7f654ae2d8db7dac7bf2ef1b6be53 100644 (file)
--- a/docs/x11/install.txt
+++ b/docs/x11/install.txt
@@ -1,5 +1,5 @@
-wxWidgets 2.6.1 for X11 installation
-------------------------------------
+wxWidgets for X11 installation
+------------------------------

 
 IMPORTANT NOTE:
 
 
 IMPORTANT NOTE:
 


@@ -11,7 +11,7 @@ IMPORTANT NOTE:
 
   When sending bug reports tell us what version of wxWidgets you are 
   using (including the beta) and what compiler on what system. One 
 
   When sending bug reports tell us what version of wxWidgets you are 
   using (including the beta) and what compiler on what system. One 

-  example: wxX11 2.6.1, gcc 2.95.4, Redhat 6.2
+  example: wxX11 2.8.0, gcc 2.95.4, Redhat 6.2

 
 First steps
 -----------
 
 First steps
 -----------


@@ -217,6 +217,20 @@ untested).
 
 The SGI native compiler support has only been tested on Irix 6.5.
 
 
 The SGI native compiler support has only been tested on Irix 6.5.
 

+* Building wxX11 on Cygwin
+--------------------------
+
+The normal build instructions should work fine on Cygwin. The one difference
+with Cygwin is that when using the "--enable-shared" configure option (which
+is the default) the API is exported explicitly using __declspec(dllexport)
+rather than all global symbols being available.
+
+This shouldn't make a difference using the library and should be a little
+more efficient. However if an export attribute has been missed somewhere you
+will see linking errors. If this happens then you can work around the
+problem by setting LDFLAGS=-Wl,--export-all-symbols. Please also let us know
+about it on the wx-dev mailing list.
+

 * Create your configuration
 ---------------------------
 
 * Create your configuration
 ---------------------------