On 10/18/07, Boris Kolpackov <[EMAIL PROTECTED]> wrote:
> Some thought on what would be good to have covered:
>
> - Building using both cygwin (-mno-cygwin) and msys toolchains.
Hello Boris,
I'm having trouble getting the mingw version to build from cygwin. I
asked a question on the users list. Until I can figure out the proper
incovation of ./runConfigure to make that happen I can not document
that part.
Below is the patch of what I have so far. I have to venture into
building the static lib and document the other bug you mentioned.
Regards,
Justin Dearing
Index: build-winunix.xml
===================================================================
--- build-winunix.xml (revision 591873)
+++ build-winunix.xml (working copy)
@@ -24,6 +24,7 @@
<li><link anchor="WinNT">Building on Windows using Microsoft
Visual C++</link></li>
<li><link anchor="UNIX">Building on UNIX/Linux/Mac OS X
platforms</link></li>
<li><link anchor="CygWin">Building on Windows using Cygwin</link></li>
+ <li><link anchor="MinGW">Building on Windows using MinGW</link></li>
<li><link anchor="WinBorlandCC">Building on Windows using
Borland C++</link></li>
<li><link anchor="WinBorlandBuilder">Building on Windows using
Borland C++ Builder</link></li>
<li><link anchor="WinIntel">Building 64 bit libraries on
Windows using Intel C++</link></li>
@@ -155,7 +156,12 @@
<p>Next set your &XercesCName; root path as follows:</p>
<source>export XERCESCROOT=<full-path-to-&XercesCSrcInstallDir;></source>
- <p>This should be the full path of the directory where
you extracted &XercesCName;.</p>
+ <p>This should be the full path of the directory where
you extracted &XercesCName;.
+ Note that this path should not have any spaces in it or
the build process will fail. The
+ only unix envirorments where this is likely to occur in are
+ <link anchor="CygWin">MinGW</link> and <link
anchor="MinGW">Cygwin</link> as the home
+ directories are by default '/home/User Name' and on
windows user names can, and often
+ do, contain spaces.</p>
</s3>
<s3 title="Building &XercesCName; library">
@@ -492,6 +498,34 @@
is recommended that you use gcc 3.1 or higher.</p>
</s2>
+ <anchor name="MinGW"/>
+ <s2 title="Building on Windows using MinGW">
+ <p><em>Do not jump into the build directly before reading
this.</em></p>
+
+ <p>&XercesCName; may be built in the
+ <jump href="http://www.mingw.org/msys.shtml";>MSYS-MinGW</jump>
environment for use
+ by Windows applications. As with the <jump
href="#UNIX">UNIX</jump>
+ platforms, &XercesCName; on MinGW uses
+ <jump href="http://www.gnu.org";>GNU</jump> tools. Therefore,
with a
+ couple of notable exceptions, &XercesCName; on MinGW is built
using
+ the same instructions as the UNIX platforms. The build
environment
+ variable XERCESCROOT must be set to the proper path containing
the
+ &XercesCName; sources and <em>runConfigure</em> must be run
with the
+ "-pmingw-msys -cgcc -xg++" arguments.</p>
+
+ <p>Note that MinGW is different from the UNIX platforms in the
way
+ that it finds libraries at run time. While UNIX platforms may
use the
+ environment variable LD_LIBRARY_PATH, Cygwin uses the PATH
environment
+ variable.</p>
+
+ <p>There is an issue with the
+ <jump
href="http://www.gnu.org/software/gcc/gcc.html";>gcc/g++</jump>
+ compiler version 2.95, where C++ exceptions thrown from a dll
will
+ cause the application to crash, regardless of whether there is
a "catch"
+ statement. This bug doesn't occur in tests using gcc 3.1 or
3.2, so it
+ is recommended that you use gcc 3.1 or higher.</p>
+ </s2>
+
<anchor name="WinBorlandBuilder"/>
<s2 title="Building on Windows using Borland C++ Builder">
<p>&XercesCName; source distribution comes with Borland C++
Builder 6 projects to help you
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
