You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by am...@apache.org on 2007/08/24 17:57:45 UTC
svn commit: r569428 [1/2] - in /xerces/c/branches/xerces-2.7/doc: ./ html/
html/apiDocs/ style/dtd/
Author: amassari
Date: Fri Aug 24 08:57:45 2007
New Revision: 569428
URL: http://svn.apache.org/viewvc?rev=569428&view=rev
Log:
Documentation update. Patch by Boris Kolpackov
Modified:
xerces/c/branches/xerces-2.7/doc/build-misc.xml
xerces/c/branches/xerces-2.7/doc/build-winunix.xml
xerces/c/branches/xerces-2.7/doc/build.xml
xerces/c/branches/xerces-2.7/doc/html/apiDocs/header.html
xerces/c/branches/xerces-2.7/doc/html/download.html
xerces/c/branches/xerces-2.7/doc/install.xml
xerces/c/branches/xerces-2.7/doc/migration.xml
xerces/c/branches/xerces-2.7/doc/migration_archive.xml
xerces/c/branches/xerces-2.7/doc/readme.xml
xerces/c/branches/xerces-2.7/doc/releases_plan.xml
xerces/c/branches/xerces-2.7/doc/style/dtd/entities.ent
xerces/c/branches/xerces-2.7/doc/xerces-c_book.xml
Modified: xerces/c/branches/xerces-2.7/doc/build-misc.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/build-misc.xml?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/build-misc.xml (original)
+++ xerces/c/branches/xerces-2.7/doc/build-misc.xml Fri Aug 24 08:57:45 2007
@@ -22,7 +22,7 @@
<anchor name="ICUPerl"/>
<s2 title="Building &XercesCName; with ICU">
<p>&XercesCName; may be built in stand-alone mode using
- native encoding support and also using ICU where you get support over 180
+ native encoding support and also using ICU where you get support for over 180
different encodings and/or locale specific message support. ICU stands for
International Components for Unicode and is an open source distribution from
IBM. You can get
Modified: xerces/c/branches/xerces-2.7/doc/build-winunix.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/build-winunix.xml?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/build-winunix.xml (original)
+++ xerces/c/branches/xerces-2.7/doc/build-winunix.xml Fri Aug 24 08:57:45 2007
@@ -19,183 +19,102 @@
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<s1 title="Building on Windows and UNIX">
+
+ <ul>
+ <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="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>
+ </ul>
+
<anchor name="WinNT"/>
- <s2 title="Building &XercesCName; on Windows using Microsoft Visual C++">
- <p>&XercesCName; source distribution comes with Microsoft Visual C++ projects and workspaces to
+ <s2 title="Building on Windows using Microsoft Visual C++">
+ <p>&XercesCName; source distribution comes with Microsoft Visual C++ projects and solutions to
help you build &XercesCName;. The following describes the steps you need
to build &XercesCName;.</p>
<s3 title="Building &XercesCName; library">
<p>To build &XercesCName; from the source distribution (using MSVC), you will
- need to open the workspace containing the project. If you are
+ need to open the solution containing the project. If you are
building your application, you may want to add the &XercesCName;
- project inside your application's workspace.</p>
- <p>The workspace containing the &XercesCName; project file and
- all other samples is in:</p>
- <p>For MSVC Version 6:</p>
-<source>&XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\xerces-all.dsw</source>
- <p>For MSVC Version 7 (Visual C++.Net):</p>
-<source>&XercesCSrcInstallDir;\Projects\Win32\VC7\xerces-all\xerces-all.sln</source>
-
- <p>Once you are inside MSVC, you need to build the project marked
- <em>XercesLib</em>.</p>
- <p>If you want to include the &XercesCName; project separately,
- you need to pick up:</p>
-<source>(For MSVC V6) &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsp
-(For MSVC V7) &XercesCSrcInstallDir;\Projects\Win32\VC7\xerces-all\XercesLib\XercesLib.vcproj</source>
- <p>You must make sure that you are linking your application with
- the &XercesCWindowsLib;.lib library and also make sure that
- the associated DLL is somewhere in your path.</p>
- <note>If you are working on the AlphaWorks version which uses ICU,
- you must have the ICU data DLL named <code>icudata.dll</code> available from your path
- setting. For finding out where you can
- get ICU from and build it, look at the <jump href="build-misc.html#faq-1">How to Build ICU</jump>.</note>
+ project inside your application's solution.</p>
+ <p>The solutions containing the &XercesCName; project files and
+ all other samples are in the following sub-directories in the
+ &XercesCSrcInstallDir; directory:</p>
- </s3>
- <s3 title="Building samples">
- <p>If you are using the source package, inside the same workspace (xerces-all.dsw), you'll find several other
- projects. These are for the samples. Select all the samples and right click
- on the selection. Then choose "Build (selection only)" to build all the
- samples in one shot.</p>
-
- <p>If you are using the binary package, load the &XercesCInstallDir;-win32\samples\Projects\Win32\VC6\samples.dsw
- Microsoft Visual C++ workspace inside your MSVC IDE. Then select all the samples and right click
- on the selection. Then choose "Build (selection only)" to build all the
- samples in one shot.</p>
- </s3>
- </s2>
-
- <anchor name="WinIntel"/>
- <s2 title="Building &XercesCName; 64 bit binary on Windows XP using Intel C++ Compiler">
- <p>&XercesCName; source distribution comes with Microsoft Visual C++ NMake Files which
- work with Intel C++ Compiler. The following describes the steps you need
- to build &XercesCName; 64 bit binary using Intel C++ Compiler.</p>
-
- <s3 title="Building &XercesCName; library">
- <p>&XercesCName; source distribution provides a makefile <code>all.mak</code>
- which will build everything including samples, tests and the parser library.</p>
<source>
-cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\all
-nmake -f all.mak "CFG=all - Win64 Release" CPP=ecl.exe
+(For VC6) Projects\Win32\VC6\xerces-all\xerces-all.dsw
+(For VC7.1) Projects\Win32\VC7.1\xerces-all\xerces-all.sln
+(For VC8) Projects\Win32\VC8\xerces-all\xerces-all.sln
</source>
- <p>If you want to just build the &XercesCName; parser library alone, then</p>
+ <p>Once you have the solution open, you need to build the
+ project marked <em>XercesLib</em>. You can select
+ Debug/Release, Static/DLL, and, for VC8, 32/64 bit
+ builds using the Configuration Manager dialog.</p>
+
+ <p>If you want to include the &XercesCName; project into
+ your own solution, you need to pick up:</p>
<source>
-cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\XercesLib
-nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
+(For VC6) Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsp
+(For VC7.1) Projects\Win32\VC7.1\xerces-all\XercesLib\XercesLib.vcproj
+(For VC8) Projects\Win32\VC8\xerces-all\XercesLib\XercesLib.vcproj
</source>
<p>You must make sure that you are linking your application with
- the &XercesCWindowsLib;.lib library and also make sure that
- the associated DLL is somewhere in your path.</p>
- </s3>
- </s2>
-
- <anchor name="WinBorlandBuilder"/>
- <s2 title="Building &XercesCName; on Windows using Borland C++Builder">
- <p>&XercesCName; source distribution comes with Borland C++Builder6 projects to help you
- build &XercesCName;. The following describes the steps you need to build
- &XercesCName;.</p>
-
- <s3 title="Building &XercesCName; library">
- <p> The library and demo projects are all contained in the Xerces-all project group:
- </p>
-
- <ul>
- <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\Xerces-all.bpg </li>
- </ul>
-
- <p> Each project in the group refers a directory below \Xerces-all.
- For example, the XercesLib project files are contained in the directory
- </p>
-
- <ul>
- <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\XercesLib </li>
- </ul>
+ the &XercesCWindowsLib;.lib library (or Debug/Static version of it
+ and also make sure that the associated DLL is somewhere in your
+ path.</p>
+
+ <note>If you are linking your application to a static library,
+ then you will need to compile your application with the
+ XML_LIBRARY preprocessor define in order
+ to turn off the DLL import/export mechanism. This is
+ also the case for the Mingw-msys platform.</note>
- <p> To build any project, open the project manager. Double click on the project
- name. Then select "Project|Build" from the menu. For example, double click
- on XercesLib.dll in the manager. Then select "Project|Build XercesLib" from
- the menu.
-
- Once the library has been built, include XercesLib.lib with in application's
- project and place XercesLib.dll somewhere in your path.
- </p>
+ <note>If you are working on the AlphaWorks version which uses ICU,
+ you must have the ICU data DLL named <code>icudata.dll</code>
+ available from your path setting. For finding out where you
+ can get ICU from and build it, look at the
+ <jump href="build-misc.html#faq-1">How to Build ICU</jump>.</note>
+
+ <note>If the library is built with the ICU message loader,
+ or message catalog loader, then you need to make sure
+ the XERCESC_NLS_HOME environment variable points to the
+ $XERCESCROOT/msg directory where the message files reside.</note>
</s3>
- </s2>
-
- <anchor name="WinBorlandCC"/>
- <s2 title="Building &XercesCName; on Windows using Borland C++ Compiler">
- <p>&XercesCName; source distribution comes with Borland C++ Compiler make files to help you
- build &XercesCName;. The following describes the steps you need to build
- &XercesCName;.</p>
-
- <ol>
- <li>Change directory to <code> &XercesCSrcInstallDir;\Projects\Win32\BCC.551\Xerces-all</code></li>
- <li>Run <code>MakeBuildDirs.bat</code>.</li>
- <li>Then issue</li>
- <ul>
- <li><code>make -f Xerces-all.mak</code>
- <br/>to build the dll (without deprecated DOM API) and tests, or</li>
- <li><code>make -f Xerces-all.mak -DWITHDEPRDOM=Y</code>
- <br/>to build the dll with deprecated DOM API (approx. 300k larger) and tests</li>
- </ul>
- </ol>
- </s2>
-
- <anchor name="CygWin"/>
- <s2 title="Building &XercesCName; on Windows using Cygwin">
- <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.cygwin.com">Cygwin</jump> environment for use
- by Cygwin applications. As with the <jump href="#UNIX">UNIX</jump>
- platforms, &XercesCName; on Cygwin uses
- <jump href="http://www.gnu.org">GNU</jump> tools. Therefore, with a
- couple of notable exceptions, &XercesCName; on Cygwin 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
- "-pcygwin -cgcc -xg++" arguments.</p>
-
- <p>Note that Cygwin 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>
+ <s3 title="Building samples">
+ <p>If you are using the source package, inside the same solution
+ (xerces-all.dsw or xerces-all.sln), you'll find several other
+ projects. These are for the samples. Select all the samples
+ and right click on the selection. Then choose "Build (selection
+ only)" to build all the samples in one shot.</p>
+ </s3>
</s2>
<anchor name="UNIX"/>
- <s2 title="Building &XercesCName; on UNIX platforms">
+ <s2 title="Building on UNIX/Linux/Mac OS X platforms">
+
<p>&XercesCName; uses
- <jump href="http://www.gnu.org">GNU</jump> tools like
- <jump href="http://www.gnu.org/software/autoconf/autoconf.html">Autoconf</jump> and
- <jump href="http://www.gnu.org/software/make/make.html">GNU Make</jump>
- to build the system. You must first make sure you
- have these tools installed on your system before proceeding.
- If you do not have required tools, ask your system administrator
- to get them for you. These tools are free under the GNU Public License
- and may be obtained from the
- <jump href="http://www.gnu.org">Free Software Foundation</jump>.</p>
+ <jump href="http://www.gnu.org/software/make/make.html">GNU make</jump>
+ to build the libraries and samples. You must first make sure you
+ have GNU make installed on your system before proceeding. On some
+ platforms GNU make is called gmake instead of make.
+ If you do not have GNU make, ask your system administrator
+ to get it for you.</p>
<p><em>Do not jump into the build directly before reading this.</em></p>
- <p>Spending some time reading the following instructions will save you a
- lot of wasted time and support-related e-mail communication.
+ <p>Spending some time reading the following instructions will save
+ you a lot of wasted time and support-related e-mail communication.
The &XercesCName; build instructions are a little different from
normal product builds. Specifically, there are some wrapper-scripts
that have been written to make life easier for you. You are free
- not to use these scripts and use
- <jump href="http://www.gnu.org/software/autoconf/autoconf.html">Autoconf</jump> and
- <jump href="http://www.gnu.org/software/make/make.html">GNU Make</jump>
- directly, but we want to make sure you
+ not to use these scripts and use the configure script and
+ GNU Make directly, but we want to make sure you
<jump href="#runConfigure-example">know what you are by-passing</jump>
and what risks you are taking. So read the following instructions
carefully before attempting to build it yourself.</p>
@@ -234,96 +153,91 @@
compiler invocation command without any parameters (e.g. xlc_r, or g++, or cc)
and check if you get a proper response back.</p>
<p>Next set your &XercesCName; root path as follows:</p>
-<source>export XERCESCROOT=<full path to &XercesCSrcInstallDir;></source>
+<source>export XERCESCROOT=<full-path-to-&XercesCSrcInstallDir;></source>
<p>This should be the full path of the directory where you extracted &XercesCName;.</p>
</s3>
<s3 title="Building &XercesCName; library">
<p>As mentioned earlier, to build &XercesCName; from the source distribution,
- you must be ready with the GNU tools like
- <jump href="http://www.gnu.org/software/autoconf/autoconf.html">autoconf</jump> and
- <jump href="http://www.gnu.org/software/make/make.html">gmake</jump>
- before you attempt the build.</p>
-
- <p>The autoconf tool is required on only one platform and produces
- a set of portable scripts (configure) that you can run on all
- other platforms without actually having the autoconf tool installed
- everywhere. In all probability the autoconf-generated script
- (called <code>configure</code>) is already in your <code>src/xercesc</code>
- directory. If not, type:</p>
-
-<source>cd $XERCESCROOT/src/xercesc
-autoconf</source>
-
- <p>This generates a shell-script called <code>configure</code>. It is tempting to run
- this script directly as is normally the case, but wait a minute.
-Even if you are
+ you will need GNU make.</p>
+
+ <p>If you look into the src/xercesc sub-directory in &XercesCSrcInstallDir;,
+ you will notice the familiar configure script. It is tempting to run
+ this script directly as is normally the case, but wait a minute.
+ Even if you are
using the default compilers like
<jump href="http://www.gnu.org/software/gcc/gcc.html">gcc</jump> and
- <jump href="http://www.gnu.org/software/gcc/gcc.html">g++</jump>
+ <jump href="http://www.gnu.org/software/gcc/gcc.html">g++</jump>
you need to export a few more
environment variables before you can invoke configure.</p>
<p>Rather than make you to figure out what strange environment
variables you need to use, we have provided you with a wrapper
- script that does the job for you. All you need to tell the script
- is what your compiler is, and what options you are going to use
+ script that does the job for you. All you need to do is tell
+ the script what your compiler is, and what options you are going to use
inside your build, and the script does everything for you. Here
is what the script takes as input:</p>
<source>
-runConfigure: Helper script to run "configure" for one of the supported platforms
+runConfigure: Helper script to run "configure" for one of the
+ supported platforms
Usage: runConfigure "options"
where options may be any of the following:
- -p <platform> (accepts 'aix', 'linux', 'freebsd',
- 'netbsd', 'solaris', 'hp-10', 'hp-11', 'openserver', 'unixware',
- 'os400', 'irix', 'ptx', 'tru64', 'macosx, 'cygwin', 'qnx')
- [required: no default]
- -c <C compiler name> (e.g. gcc, cc, xlc_r, icc or ecc)
+ -p <platform> (accepts 'aix', 'beos', 'linux', 'freebsd',
+ 'netbsd', 'solaris', 'hp-10', 'hp-11', 'openserver', 'unixware',
+ 'os400', 'os390', 'irix', 'ptx', 'tru64', 'macosx', 'cygwin',
+ 'qnx', 'interix', 'mingw-msys')
+ [required; no default]
+ -c <C compiler name> (e.g. gcc, cc, xlc_r, qcc, icc, icpc or ecc)
[default is make default; cc for gnu make]
- -x <C++ compiler name> (e.g. g++, CC, aCC, xlC_r, QCC
- icc or ecc) [default is make default; g++ for gnu make]
+ -x <C++ compiler name> (e.g. g++, CC, aCC, xlC_r, xlC_rv5compat, QCC,
+ icc, icpc or ecc) [default is make default; g++ for gnu make]
-d (specifies that you want to build debug version)
[default: no debug]
- -m <message loader> can be 'inmem', 'icu', 'MsgFile' or
+ -m <message loader> can be 'inmem', 'icu', 'MsgFile' or
'iconv' [default: inmem]
- -n <net accessor> can be 'fileonly', 'libwww', 'socket' or
+ -n <net accessor> can be 'fileonly', 'libwww', 'socket', 'winsock' or
'native' [default: socket]
- -t <transcoder> can be 'icu', 'Iconv400', 'Uniconv390',
+ -t <transcoder> can be 'icu', 'Iconv400', 'Uniconv390', 'Win32',
'IconvFBSD', 'IconvGNU' or 'native'
[default: native]
- -r <thread option> can be 'pthread' or 'dce'
+ -r <thread option> can be 'pthread' or 'dce'
(AIX, HP-11, and Solaris) or 'sproc' (IRIX) or 'none'
[default: pthread]
- -b <bitsToBuild> (accepts '64', '32') [default: 32]
- -l <extra linker options>
- -z <extra compiler options>
- -P <install-prefix>
- -C <any one extra configure options>
+ -s (specifies that you want to build static libraries) [default: shared]
+ -b <bitsToBuild> (accepts '64', '32') [default: 32]
+ -l <extra linker options>
+ -z <extra compiler options>
+ -P <install-prefix>
+ -C <any one extra configure options>
-h (get help on the above commands)
</source>
<note>&XercesCName; can be built as either a standalone library or as a library
- dependent on International Components for Unicode (ICU). For simplicity,
- the following discussion only explains standalone builds.</note>
+ dependent on International Components for Unicode (ICU). For simplicity, the
+ following discussion only explains standalone builds.</note>
<anchor name="runConfigure-example"/>
<p>Some additional explanation may be helpful for some of the options:</p>
<ul><li><em>-m <message loader>, -t <transcoder> </em>
<br />If you specify <code>icu</code> as the value for either of
these options, you must already have set the
- environment variable ICUROOT</li>
+ environment variable ICUROOT to point to the ICU distribution directory.</li>
<li><em>-n <net accessor></em>
<br />The default value <code>socket</code> handles HTTP URL's.
- The value <code>native</code> is only supported for macosx.
+ The value <code>native</code> is only supported for Mac OS X. The
+ value <code>winsock</code> is only supported on Mingw-msys.
</li>
</ul>
<p>One of the common ways to build &XercesCName; is as follows:</p>
-<source>runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread</source>
+<source>
+cd src/xercesc
+./runConfigure -plinux -cgcc -xg++ -minmem -nsocket -tnative -rpthread
+</source>
- <p>The response will be something like the following (extra line
+ <p>The response will be something like the following (extra line
breaks have been added for readability). See especially the end,
which tells you how <em>configure</em> was invoked.</p>
<source>
@@ -335,86 +249,102 @@
Net Accessor: socket
Transcoder: native
Thread option: pthread
+Library type: shared
bitsToBuild option: 32
Extra compile options:
Extra link options:
Extra configure options:
Debug is OFF
-creating cache ./config.cache
checking for gcc... gcc
-checking whether the C compiler
- (gcc -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
- -DXML_USE_NETACCESSOR_SOCKET ) works... yes
-checking whether the C compiler
- (gcc -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
- -DXML_USE_NETACCESSOR_SOCKET ) is a cross-compiler... no
-checking whether we are using GNU C... yes
+checking for C compiler default output file name... a.out
+checking whether the C compiler works... yes
+checking whether we are cross compiling... no
+checking for suffix of executables...
+checking for suffix of object files... o
+checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
-checking for c++... g++
-checking whether the C++ compiler
- (g++ -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
- -DXML_USE_NETACCESSOR_SOCKET ) works... yes
-checking whether the C++ compiler
- (g++ -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
- -DXML_USE_NETACCESSOR_SOCKET ) is a cross-compiler... yes
-checking whether we are using GNU C++... yes
+checking for gcc option to accept ISO C89... none needed
+checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
-checking for a BSD compatible install... /usr/bin/install -c
+checking for a BSD-compatible install... /usr/bin/install -c
checking for autoconf... autoconf
checking how to run the C preprocessor... gcc -E
+checking for grep that handles long lines and -e... /bin/grep
+checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
+checking for sys/types.h... yes
+checking for sys/stat.h... yes
+checking for stdlib.h... yes
+checking for string.h... yes
+checking for memory.h... yes
+checking for strings.h... yes
+checking for inttypes.h... yes
+checking for stdint.h... yes
+checking for unistd.h... yes
checking for XMLByte... no
-checking host system type... i686-pc-linux-gnu
-updating cache ./config.cache
-creating ./config.status
-creating Makefile
-creating util/Makefile
-creating util/Transcoders/ICU/Makefile
-creating util/Transcoders/Iconv/Makefile
-creating util/Transcoders/Iconv390/Makefile
-creating util/Transcoders/Uniconv390/Makefile
-creating util/Transcoders/Iconv400/Makefile
-creating util/Transcoders/IconvFBSD/Makefile
-creating util/Transcoders/MacOSUnicodeConverter/Makefile
-creating util/Platforms/Makefile
-creating util/Platforms/Solaris/Makefile
-creating util/Platforms/AIX/Makefile
-creating util/Platforms/Linux/Makefile
-creating util/Platforms/FreeBSD/Makefile
-creating util/Platforms/HPUX/Makefile
-creating util/Platforms/OS390/Makefile
-creating util/Platforms/OS400/Makefile
-creating util/Platforms/IRIX/Makefile
-creating util/Platforms/PTX/Makefile
-creating util/Platforms/OpenServer/Makefile
-creating util/Platforms/UnixWare/Makefile
-creating util/Platforms/Tru64/Makefile
-creating util/Platforms/MacOS/Makefile
-creating util/Compilers/Makefile
-creating util/MsgLoaders/InMemory/Makefile
-creating util/MsgLoaders/ICU/Makefile
-creating util/MsgLoaders/MsgCatalog/Makefile
-creating util/MsgLoaders/MsgFile/Makefile
-creating util/NetAccessors/Socket/Makefile
-creating util/NetAccessors/libWWW/Makefile
-creating util/NetAccessors/MacOSURLAccessCF/Makefile
-creating util/regx/Makefile
-creating validators/Makefile
-creating validators/common/Makefile
-creating validators/datatype/Makefile
-creating validators/DTD/Makefile
-creating validators/schema/Makefile
-creating validators/schema/identity/Makefile
-creating framework/Makefile
-creating dom/Makefile
-creating dom/impl/Makefile
-creating dom/deprecated/Makefile
-creating parsers/Makefile
-creating internal/Makefile
-creating sax/Makefile
-creating sax2/Makefile
-creating ../../obj/Makefile
+checking build system type... i686-unknown-linux-gnu
+checking host system type... i686-unknown-linux-gnu
+configure: creating ./config.status
+config.status: creating Makefile
+config.status: creating util/Makefile
+config.status: creating util/Transcoders/Cygwin/Makefile
+config.status: creating util/Transcoders/Win32/Makefile
+config.status: creating util/Transcoders/ICU/Makefile
+config.status: creating util/Transcoders/Iconv/Makefile
+config.status: creating util/Transcoders/Iconv390/Makefile
+config.status: creating util/Transcoders/Uniconv390/Makefile
+config.status: creating util/Transcoders/Iconv400/Makefile
+config.status: creating util/Transcoders/IconvFBSD/Makefile
+config.status: creating util/Transcoders/IconvGNU/Makefile
+config.status: creating util/Transcoders/MacOSUnicodeConverter/Makefile
+config.status: creating util/Platforms/Makefile
+config.status: creating util/Platforms/Solaris/Makefile
+config.status: creating util/Platforms/AIX/Makefile
+config.status: creating util/Platforms/BeOS/Makefile
+config.status: creating util/Platforms/QNX/Makefile
+config.status: creating util/Platforms/Linux/Makefile
+config.status: creating util/Platforms/FreeBSD/Makefile
+config.status: creating util/Platforms/NetBSD/Makefile
+config.status: creating util/Platforms/HPUX/Makefile
+config.status: creating util/Platforms/OS390/Makefile
+config.status: creating util/Platforms/OS400/Makefile
+config.status: creating util/Platforms/IRIX/Makefile
+config.status: creating util/Platforms/PTX/Makefile
+config.status: creating util/Platforms/OpenServer/Makefile
+config.status: creating util/Platforms/UnixWare/Makefile
+config.status: creating util/Platforms/Tru64/Makefile
+config.status: creating util/Platforms/MacOS/Makefile
+config.status: creating util/Platforms/Win32/Makefile
+config.status: creating util/Platforms/Cygwin/Makefile
+config.status: creating util/Compilers/Makefile
+config.status: creating util/MsgLoaders/InMemory/Makefile
+config.status: creating util/MsgLoaders/ICU/Makefile
+config.status: creating util/MsgLoaders/ICU/resources/Makefile
+config.status: creating util/MsgLoaders/MsgCatalog/Makefile
+config.status: creating util/MsgLoaders/MsgFile/Makefile
+config.status: creating util/NetAccessors/Socket/Makefile
+config.status: creating util/NetAccessors/WinSock/Makefile
+config.status: creating util/NetAccessors/libWWW/Makefile
+config.status: creating util/NetAccessors/MacOSURLAccessCF/Makefile
+config.status: creating util/regx/Makefile
+config.status: creating validators/Makefile
+config.status: creating validators/common/Makefile
+config.status: creating validators/datatype/Makefile
+config.status: creating validators/DTD/Makefile
+config.status: creating validators/schema/Makefile
+config.status: creating validators/schema/identity/Makefile
+config.status: creating framework/Makefile
+config.status: creating framework/psvi/Makefile
+config.status: creating dom/Makefile
+config.status: creating dom/impl/Makefile
+config.status: creating dom/deprecated/Makefile
+config.status: creating parsers/Makefile
+config.status: creating internal/Makefile
+config.status: creating sax/Makefile
+config.status: creating sax2/Makefile
+config.status: creating ../../obj/Makefile
+config.status: executing default commands
Having build problems?
Read instructions at http://xerces.apache.org/xerces-c/build.html
@@ -422,25 +352,32 @@
Find out if someone else had the same problem before.
Go to http://marc.theaimsgroup.com/?l=xerces-c-dev
-In future, you may also directly type the following commands to create the Makefiles.
+In future, you may also directly type the following commands to create
+the Makefiles.
export TRANSCODER="NATIVE"
export MESSAGELOADER="INMEM"
export NETACCESSOR="Socket"
export THREADS="pthread"
+export LIBTYPE="shared"
export BITSTOBUILD="32"
export CC="gcc"
export CXX="g++"
-export CXXFLAGS=" -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER
- -DXML_USE_PTHREADS -DXML_USE_NETACCESSOR_SOCKET "
-export CFLAGS=" -w -O -DXML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER
- -DXML_USE_PTHREADS -DXML_USE_NETACCESSOR_SOCKET "
+export CXXFLAGS=" -w -O2 -DNDEBUG -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS
+ -DPROJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM -DPROJ_DEPRECATED_DOM -DPROJ_VALIDATORS -DX
+ML_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS -DXML_
+USE_NETACCESSOR_SOCKET "
+export CFLAGS=" -w -O2 -DNDEBUG -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -
+DPROJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM -DPROJ_DEPRECATED_DOM -DPROJ_VALIDATORS -DXML
+_USE_NATIVE_TRANSCODER -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS -DXML_US
+E_NETACCESSOR_SOCKET "
export LDFLAGS=" "
export LIBS=" -lpthread "
configure
If the result of the above commands look OK to you, go to the directory
-$HOME/&XercesCSrcInstallDir;/src/xercesc and type "gmake" to make the XERCES-C system.</source>
+src/xercesc and type "make" (or "gmake") to make the XERCES-C system.
+</source>
<p>So now you see what the wrapper script has actually been doing! It has
invoked <code>configure</code>
@@ -450,100 +387,193 @@
<p>Now that the Makefiles are all created, you are ready to do the actual build.</p>
-<source>gmake</source>
+<source>make</source>
+
+ <p>Is that it? Yes, that's all you need to build &XercesCName;. The libraries
+ can be found in the lib sub-directory </p>
+
+ <note>If the library is built with the ICU message loader,
+ or message catalog loader, then you need to make sure
+ the XERCESC_NLS_HOME environment variable points to the
+ $XERCESCROOT/msg directory where the message files reside.</note>
- <p>Is that it? Yes, that's all you need to build &XercesCName;.</p>
</s3>
<s3 title="Building samples">
- <p>The installation process for the samples is same on all UNIX
- platforms.
+ <p>The building process for the samples is similar to building
+ the Xerces-C++ libraries. The samples directory contains the
+ runConfigure script which is very similar to the one found
+ in src/xercesc except it has fewer options. To see available
+ options, run:
</p>
-<source>cd &XercesCInstallDir;-linux/samples
-./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
-gmake</source>
- <p>This will create the object files in each sample directory
- and the executables in ' &XercesCInstallDir;-linux/bin' directory.</p>
-
- <p>Note that <em>runConfigure</em> is just a helper script and you are free to
- use <em>./configure</em> with the correct parameters to make it work
- on any platform-compiler combination of your choice. The script needs the following parameters:
- </p>
<source>
-runConfigure: Helper script to run "configure" for one of the supported platforms
-Usage: runConfigure "options"
- where options may be any of the following:
- -p <platform> (accepts 'aix', 'beos', 'linux', 'freebsd', 'netbsd',
- 'solaris', 'hp-10', 'hp-11', 'openserver', 'unixware',
- 'os400', 'irix', 'ptx', 'tru64', 'macosx', 'cygwin')
- [required; no default]
- -c <C compiler name> (e.g. gcc, cc, xlc_r, icc or ecc)
- [default is make default; cc for gnu make]
- -x <C++ compiler name> (e.g. g++, CC, aCC, xlC_r, QCC,
- icc or ecc) [default is make default; g++ for gnu make]
- -d (specifies that you want to build debug version) [default: not debug]
- -r <thread option> can be 'pthread' or 'dce'
- (AIX, HP-11, and Solaris) or 'sproc' (IRIX) or 'none'
- [default: pthread]
- -b <bitsToBuild> (accepts '64', '32') [default: 32]
- -l <extra linker options>
- -z <extra compiler options>
- -h (get help on the above commands)
+cd samples
+./runConfigure -h
</source>
- <note><em>NOTE:</em>The code samples in this section assume that you are working on the Linux binary drop.
- If you are using some other UNIX flavor, please replace '-linux' with the appropriate
- platform name in the code samples.</note>
+ <p>To continue our build procedure from the previous section,
+ we execute runConfigure with the following options:</p>
- <p>To delete all the generated object files and executables, type:</p>
-<source>gmake clean</source>
+<source>
+./runConfigure -plinux -cgcc -xg++ -rpthread
+</source>
+
+ <p>After that we can run GNU make to build the samples:</p>
+
+<source>
+make
+</source>
+
+ <p>The sample executable can be found in the bin sub-directory in
+ &XercesCSrcInstallDir;. To delete all the generated object
+ files and executables, run:</p>
+<source>
+make clean
+</source>
+ </s3>
+
+
+ <s3 title="Building a single-threaded library">
+ <p>To build Xerces-C++ as a single-threaded library on UNIX platforms you
+ have to pass the -rnone option to runConfigure. The following additional
+ steps are neccessary for certain platforms:</p>
+
+ <p>For Aix - </p>
+ <ul>
+ <li>Replace <code>xlc_r</code> and <code>xlC_r</code> compilers with
+ <code>xlc</code> and <code>xlC</code> respectively</li>
+ <li>Replace <code>makeC++SharedLib_r</code> with <code>makeC++SharedLib</code> in
+ Makefile.incl</li>
+ <li>Remove the <code>-D_THREAD_SAFE</code> and <code>-D_REENTRANT</code> compiler flags in Makefile.incl</li>
+ </ul>
+
+ <p>For Solaris -</p>
+ <ul>
+ <li>Remove the <code>-mt</code> and <code>-D_REENTRANT</code> compiler flags in Makefile.incl</li>
+ </ul>
+
+ <p>For Linux -</p>
+ <ul>
+ <li>Remove the <code>-D_REENTRANT</code> compiler flag in Makefile.incl</li>
+ </ul>
+
+ <p>For HP-UX -</p>
+ <ul>
+ <li>Remove the <code>-D_REENTRANT</code> and <code>-mt</code> compiler flags in Makefile.incl.</li>
+ </ul>
+
+ <p>For Mac OS X -</p>
+ <ul>
+ <li>Remove the <code>-D_REENTRANT</code> compiler flag in Makefile.incl.</li>
+ </ul>
</s3>
</s2>
- <anchor name="UNIX_SingleThread"/>
- <s2 title="Building &XercesCName; as a single-threaded library on Unix platforms">
- <p>To build a single-threaded library on Unix platforms you have to update
- one or more of the following files <code>Makefile.incl, Makefile.in, runConfigure</code>.
- The following steps guide you to create a single-threaded library for each platform:</p>
-
- <p>For Aix - </p>
- <ul>
- <li>Replace <code>xlc_r</code> and <code>xlC_r</code> libraries with
- <code>xlc</code> and <code>xlC</code> respectively</li>
- <li>Replace <code>makeC++SharedLib_r</code> with <code>makeC++SharedLib</code></li>
- <li>Remove the flag <code>-D_THREAD_SAFE</code></li>
- <li>Remove inclusion of any threaded library directories from the <code>LIBPATH</code></li>
- <li>Remove inclusion of <code>-lpthreads</code> and <code>-lpthread_compat</code></li>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under AIX specific options
- in <code>Makefile.incl</code></li>
- </ul>
-
- <p>For Solaris -</p>
- <ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under SOLARIS
- specific options in <code>Makefile.incl</code></li>
- <li>Remove compiler switch <code>-mt</code></li>
- <li>Remove <code>-D_REENTRANT</code> flag from the 'compile' options</li>
- <li>Remove inclusion of <code>-lpthread</code></li>
- </ul>
+ <anchor name="CygWin"/>
+ <s2 title="Building on Windows using Cygwin">
+ <p><em>Do not jump into the build directly before reading this.</em></p>
- <p>For Linux -</p>
- <ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under LINUX
- specific options in <code>Makefile.incl</code></li>
- <li>Remove <code>-D_REENTRANT</code> flag from the 'compile' options</li>
- <li>Remove inclusion of <code>-lpthread</code></li>
- </ul>
+ <p>&XercesCName; may be built in the
+ <jump href="http://www.cygwin.com">Cygwin</jump> environment for use
+ by Cygwin applications. As with the <jump href="#UNIX">UNIX</jump>
+ platforms, &XercesCName; on Cygwin uses
+ <jump href="http://www.gnu.org">GNU</jump> tools. Therefore, with a
+ couple of notable exceptions, &XercesCName; on Cygwin 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
+ "-pcygwin -cgcc -xg++" arguments.</p>
+
+ <p>Note that Cygwin 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>
- <p>For HPUX -</p>
- <ul>
- <li>Add <code>-DAPP_NO_THREADS</code> to define the variable under HP
- specific options in <code>Makefile.incl</code></li>
- <li>Remove inclusion of <code>-lpthread</code> and <code>-lcma</code></li>
- <li>Remove threading defines like <code>-D_PTHREADS_DRAFT4 ,
- -DXML_USE_DCE</code></li>
- </ul>
- </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
+ build &XercesCName;. The following describes the steps you need to build
+ &XercesCName;.</p>
+
+ <s3 title="Building &XercesCName; library">
+ <p> The library and demo projects are all contained in the Xerces-all project group:
+ </p>
+
+ <ul>
+ <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\Xerces-all.bpg </li>
+ </ul>
+
+ <p> Each project in the group refers a directory below \Xerces-all.
+ For example, the XercesLib project files are contained in the directory
+ </p>
+
+ <ul>
+ <li> &XercesCSrcInstallDir;\Projects\Win32\BCB6\Xerces-all\XercesLib </li>
+ </ul>
+
+ <p> To build any project, open the project manager. Double click on the project
+ name. Then select "Project|Build" from the menu. For example, double click
+ on XercesLib.dll in the manager. Then select "Project|Build XercesLib" from
+ the menu.
+
+ Once the library has been built, include XercesLib.lib with in application's
+ project and place XercesLib.dll somewhere in your path.
+ </p>
+
+ </s3>
+ </s2>
+
+ <anchor name="WinBorlandCC"/>
+ <s2 title="Building on Windows using Borland C++">
+ <p>&XercesCName; source distribution comes with Borland C++ Compiler make files to help you
+ build &XercesCName;. The following describes the steps you need to build
+ &XercesCName;.</p>
+
+ <ol>
+ <li>Change directory to <code> &XercesCSrcInstallDir;\Projects\Win32\BCC.551\Xerces-all</code></li>
+ <li>Run <code>MakeBuildDirs.bat</code>.</li>
+ <li>Then issue</li>
+ <ul>
+ <li><code>make -f Xerces-all.mak</code>
+ <br/>to build the dll (without deprecated DOM API) and tests, or</li>
+ <li><code>make -f Xerces-all.mak -DWITHDEPRDOM=Y</code>
+ <br/>to build the dll with deprecated DOM API (approx. 300k larger) and tests</li>
+ </ul>
+ </ol>
+ </s2>
+
+ <anchor name="WinIntel"/>
+ <s2 title="Building 64 bit libraries on Windows using Intel C++">
+ <p>&XercesCName; source distribution comes with Microsoft Visual C++ NMake Files which
+ work with Intel C++ Compiler. The following describes the steps you need
+ to build &XercesCName; 64 bit binary using Intel C++ Compiler.</p>
+
+ <s3 title="Building &XercesCName; library">
+ <p>&XercesCName; source distribution provides a makefile <code>all.mak</code>
+ which will build everything including samples, tests and the parser library.</p>
+<source>
+cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\all
+nmake -f all.mak "CFG=all - Win64 Release" CPP=ecl.exe
+</source>
+
+ <p>If you want to just build the &XercesCName; parser library alone, then</p>
+<source>
+cd &XercesCSrcInstallDir;\Projects\Win32\VC6\xerces-all\XercesLib
+nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
+</source>
+
+ <p>You must make sure that you are linking your application with
+ the &XercesCWindowsLib;.lib library and also make sure that
+ the associated DLL is somewhere in your path.</p>
+ </s3>
+ </s2>
</s1>
Modified: xerces/c/branches/xerces-2.7/doc/build.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/build.xml?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/build.xml (original)
+++ xerces/c/branches/xerces-2.7/doc/build.xml Fri Aug 24 08:57:45 2007
@@ -24,13 +24,12 @@
<p>Read the <jump href="build-winunix.html">Building on Windows and UNIX</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-winunix.html#WinNT">Building &XercesCName; on Windows using Microsoft Visual C++</jump></li>
- <li><jump href="build-winunix.html#WinIntel">Building &XercesCName; 64 bit binary on Windows XP using Intel C++ Compiler</jump></li>
- <li><jump href="build-winunix.html#WinBorlandBuilder">Building &XercesCName; on Windows using Borland C++Builder</jump></li>
- <li><jump href="build-winunix.html#WinBorlandCC">Building &XercesCName; on Windows using Borland C++ Compiler</jump></li>
- <li><jump href="build-winunix.html#CygWin">Building &XercesCName; on Windows using Cygwin</jump></li>
- <li><jump href="build-winunix.html#UNIX">Building &XercesCName; on UNIX platforms</jump></li>
- <li><jump href="build-winunix.html#UNIX_SingleThread">Building &XercesCName; as a single-threaded library on Unix platforms</jump></li>
+ <li><jump href="build-winunix.html#WinNT">Building on Windows using Microsoft Visual C++</jump></li>
+ <li><jump href="build-winunix.html#UNIX">Building on UNIX/Linux/Mac OS X platforms</jump></li>
+ <li><jump href="build-winunix.html#CygWin">Building on Windows using Cygwin</jump></li>
+ <li><jump href="build-winunix.html#WinBorlandCC">Building on Windows using Borland C++</jump></li>
+ <li><jump href="build-winunix.html#WinBorlandBuilder">Building on Windows using Borland C++ Builder</jump></li>
+ <li><jump href="build-winunix.html#WinIntel">Building 64 bit libraries on Windows using Intel C++</jump></li>
</ul>
</s2>
Modified: xerces/c/branches/xerces-2.7/doc/html/apiDocs/header.html
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/html/apiDocs/header.html?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/html/apiDocs/header.html (original)
+++ xerces/c/branches/xerces-2.7/doc/html/apiDocs/header.html Fri Aug 24 08:57:45 2007
@@ -6,8 +6,8 @@
<A href="../index.html" onMouseOut="rolloverOff('side-index');" onMouseOver="rolloverOn('side-index');"><IMG alt="Readme" border="0" height="12" hspace="0" name="side-index" onLoad="rolloverLoad('side-index','../graphics/index-label-2.jpg','../graphics/index-label-3.jpg');" src="../graphics/index-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="../charter.html" onMouseOut="rolloverOff('side-charter');" onMouseOver="rolloverOn('side-charter');"><IMG alt="Charter" border="0" height="12" hspace="0" name="side-charter" onLoad="rolloverLoad('side-charter','../graphics/charter-label-2.jpg','../graphics/charter-label-3.jpg');" src="../graphics/charter-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="../releases.html" onMouseOut="rolloverOff('side-releases');" onMouseOver="rolloverOn('side-releases');"><IMG alt="Release Info" border="0" height="12" hspace="0" name="side-releases" onLoad="rolloverLoad('side-releases','../graphics/releases-label-2.jpg','../graphics/releases-label-3.jpg');" src="../graphics/releases-label-3.jpg" vspace="0" width="120"></A><BR>
-
-
+
+
@@ -17,49 +17,28 @@
<A href="../install.html" onMouseOut="rolloverOff('side-install');" onMouseOver="rolloverOn('side-install');"><IMG alt="Installation" border="0" height="12" hspace="0" name="side-install" onLoad="rolloverLoad('side-install','../graphics/install-label-2.jpg','../graphics/install-label-3.jpg');" src="../graphics/install-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="http://xerces.apache.org/xerces-c/download.cgi" onMouseOut="rolloverOff('side-ext-20');" onMouseOver="rolloverOn('side-ext-20');"><IMG alt="Download" border="0" height="12" hspace="0" name="side-ext-20" onLoad="rolloverLoad('side-ext-20','../graphics/ext-20-label-2.jpg','../graphics/ext-20-label-3.jpg');" src="../graphics/ext-20-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="../build.html" onMouseOut="rolloverOff('side-build');" onMouseOver="rolloverOn('side-build');"><IMG alt="Build Instructions" border="0" height="12" hspace="0" name="side-build" onLoad="rolloverLoad('side-build','../graphics/build-label-2.jpg','../graphics/build-label-3.jpg');" src="../graphics/build-label-3.jpg" vspace="0" width="120"></A><BR>
-
-
-
+
+
+
<IMG border="0" height="6" hspace="0" src="../resources/separator.gif" vspace="0" width="120"><BR>
- <A href="../faqs.html" onMouseOut="rolloverOff('side-faqs');" onMouseOver="rolloverOn('side-faqs');"><IMG alt="FAQs" border="0" height="12" hspace="0" name="side-faqs" onLoad="rolloverLoad('side-faqs','../graphics/faqs-label-2.jpg','../graphics/faqs-label-3.jpg');" src="../graphics/faqs-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="../program.html" onMouseOut="rolloverOff('side-program');" onMouseOver="rolloverOn('side-program');"><IMG alt="Programming" border="0" height="12" hspace="0" name="side-program" onLoad="rolloverLoad('side-program','../graphics/program-label-2.jpg','../graphics/program-label-3.jpg');" src="../graphics/program-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="../samples.html" onMouseOut="rolloverOff('side-samples');" onMouseOver="rolloverOn('side-samples');"><IMG alt="Samples" border="0" height="12" hspace="0" name="side-samples" onLoad="rolloverLoad('side-samples','../graphics/samples-label-2.jpg','../graphics/samples-label-3.jpg');" src="../graphics/samples-label-3.jpg" vspace="0" width="120"></A><BR>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <A href="../api.html" onMouseOut="rolloverOff('side-api');" onMouseOver="rolloverOn('side-api');"><IMG alt="API Docs" border="0" height="12" hspace="0" name="side-api" onLoad="rolloverLoad('side-api','../graphics/api-label-2.jpg','../graphics/api-label-3.jpg');" src="../graphics/api-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="../faqs.html" onMouseOut="rolloverOff('side-faqs');" onMouseOver="rolloverOn('side-faqs');"><IMG alt="FAQs" border="0" height="12" hspace="0" name="side-faqs" onLoad="rolloverLoad('side-faqs','../graphics/faqs-label-2.jpg','../graphics/faqs-label-3.jpg');" src="../graphics/faqs-label-3.jpg" vspace="0" width="120"></A><BR>
+
<IMG border="0" height="6" hspace="0" src="../resources/separator.gif" vspace="0" width="120"><BR>
- <A href="../ApacheDOMC++Binding.html" onMouseOut="rolloverOff('side-ext-70');" onMouseOver="rolloverOn('side-ext-70');"><IMG alt="DOM C++ Binding" border="0" height="12" hspace="0" name="side-ext-70" onLoad="rolloverLoad('side-ext-70','../graphics/ext-70-label-2.jpg','../graphics/ext-70-label-3.jpg');" src="../graphics/ext-70-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="../api.html" onMouseOut="rolloverOff('side-api');" onMouseOver="rolloverOn('side-api');"><IMG alt="API Docs" border="0" height="12" hspace="0" name="side-api" onLoad="rolloverLoad('side-api','../graphics/api-label-2.jpg','../graphics/api-label-3.jpg');" src="../graphics/api-label-3.jpg" vspace="0" width="120"></A><BR>
- <IMG alt="Programming" border="0" height="12" hspace="0" src="../graphics/program-label-1.jpg" vspace="0" width="120"><BR>
-
-
-
-
-
-
-
+ <A href="../ApacheDOMC++Binding.html" onMouseOut="rolloverOff('side-ext-86');" onMouseOver="rolloverOn('side-ext-86');"><IMG alt="DOM C++ Binding" border="0" height="12" hspace="0" name="side-ext-86" onLoad="rolloverLoad('side-ext-86','../graphics/ext-86-label-2.jpg','../graphics/ext-86-label-3.jpg');" src="../graphics/ext-86-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="../migrate.html" onMouseOut="rolloverOff('side-migrate');" onMouseOver="rolloverOn('side-migrate');"><IMG alt="Migration Guide" border="0" height="12" hspace="0" name="side-migrate" onLoad="rolloverLoad('side-migrate','../graphics/migrate-label-2.jpg','../graphics/migrate-label-3.jpg');" src="../graphics/migrate-label-3.jpg" vspace="0" width="120"></A><BR>
-
-
+
+
<IMG border="0" height="6" hspace="0" src="../resources/separator.gif" vspace="0" width="120"><BR>
<A href="../feedback.html" onMouseOut="rolloverOff('side-feedback');" onMouseOver="rolloverOn('side-feedback');"><IMG alt="Feedback" border="0" height="12" hspace="0" name="side-feedback" onLoad="rolloverLoad('side-feedback','../graphics/feedback-label-2.jpg','../graphics/feedback-label-3.jpg');" src="../graphics/feedback-label-3.jpg" vspace="0" width="120"></A><BR>
@@ -68,13 +47,13 @@
<IMG border="0" height="6" hspace="0" src="../resources/separator.gif" vspace="0" width="120"><BR>
-
+
<A href="http://svn.apache.org/viewcvs.cgi/xerces/?root=Apache-SVN" onMouseOut="rolloverOff('side-ext-102');" onMouseOver="rolloverOn('side-ext-102');"><IMG alt="Source Repository" border="0" height="12" hspace="0" name="side-ext-102" onLoad="rolloverLoad('side-ext-102','../graphics/ext-102-label-2.jpg','../graphics/ext-102-label-3.jpg');" src="../graphics/ext-102-label-3.jpg" vspace="0" width="120"></A><BR>
-
+
<A href="http://marc.theaimsgroup.com/?l=xerces-c-users" onMouseOut="rolloverOff('side-ext-104');" onMouseOver="rolloverOn('side-ext-104');"><IMG alt="User Mail Archive" border="0" height="12" hspace="0" name="side-ext-104" onLoad="rolloverLoad('side-ext-104','../graphics/ext-104-label-2.jpg','../graphics/ext-104-label-3.jpg');" src="../graphics/ext-104-label-3.jpg" vspace="0" width="120"></A><BR>
-
+
<A href="http://marc.theaimsgroup.com/?l=xerces-c-dev" onMouseOut="rolloverOff('side-ext-106');" onMouseOver="rolloverOn('side-ext-106');"><IMG alt="Devel Mail Archive" border="0" height="12" hspace="0" name="side-ext-106" onLoad="rolloverLoad('side-ext-106','../graphics/ext-106-label-2.jpg','../graphics/ext-106-label-3.jpg');" src="../graphics/ext-106-label-3.jpg" vspace="0" width="120"></A><BR>
Modified: xerces/c/branches/xerces-2.7/doc/html/download.html
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/html/download.html?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/html/download.html (original)
+++ xerces/c/branches/xerces-2.7/doc/html/download.html Fri Aug 24 08:57:45 2007
@@ -45,39 +45,18 @@
<IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
- <A href="faqs.html" onMouseOut="rolloverOff('side-faqs');" onMouseOver="rolloverOn('side-faqs');"><IMG alt="FAQs" border="0" height="12" hspace="0" name="side-faqs" onLoad="rolloverLoad('side-faqs','graphics/faqs-label-2.jpg','graphics/faqs-label-3.jpg');" src="graphics/faqs-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="program.html" onMouseOut="rolloverOff('side-program');" onMouseOver="rolloverOn('side-program');"><IMG alt="Programming" border="0" height="12" hspace="0" name="side-program" onLoad="rolloverLoad('side-program','graphics/program-label-2.jpg','graphics/program-label-3.jpg');" src="graphics/program-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="samples.html" onMouseOut="rolloverOff('side-samples');" onMouseOver="rolloverOn('side-samples');"><IMG alt="Samples" border="0" height="12" hspace="0" name="side-samples" onLoad="rolloverLoad('side-samples','graphics/samples-label-2.jpg','graphics/samples-label-3.jpg');" src="graphics/samples-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="faqs.html" onMouseOut="rolloverOff('side-faqs');" onMouseOver="rolloverOn('side-faqs');"><IMG alt="FAQs" border="0" height="12" hspace="0" name="side-faqs" onLoad="rolloverLoad('side-faqs','graphics/faqs-label-2.jpg','graphics/faqs-label-3.jpg');" src="graphics/faqs-label-3.jpg" vspace="0" width="120"></A><BR>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <A href="api.html" onMouseOut="rolloverOff('side-api');" onMouseOver="rolloverOn('side-api');"><IMG alt="API Docs" border="0" height="12" hspace="0" name="side-api" onLoad="rolloverLoad('side-api','graphics/api-label-2.jpg','graphics/api-label-3.jpg');" src="graphics/api-label-3.jpg" vspace="0" width="120"></A><BR>
-
<IMG border="0" height="6" hspace="0" src="resources/separator.gif" vspace="0" width="120"><BR>
- <A href="ApacheDOMC++Binding.html" onMouseOut="rolloverOff('side-ext-70');" onMouseOver="rolloverOn('side-ext-70');"><IMG alt="DOM C++ Binding" border="0" height="12" hspace="0" name="side-ext-70" onLoad="rolloverLoad('side-ext-70','graphics/ext-70-label-2.jpg','graphics/ext-70-label-3.jpg');" src="graphics/ext-70-label-3.jpg" vspace="0" width="120"></A><BR>
-
- <IMG alt="Programming" border="0" height="12" hspace="0" src="graphics/program-label-1.jpg" vspace="0" width="120"><BR>
-
-
-
-
-
-
+ <A href="api.html" onMouseOut="rolloverOff('side-api');" onMouseOver="rolloverOn('side-api');"><IMG alt="API Docs" border="0" height="12" hspace="0" name="side-api" onLoad="rolloverLoad('side-api','graphics/api-label-2.jpg','graphics/api-label-3.jpg');" src="graphics/api-label-3.jpg" vspace="0" width="120"></A><BR>
+ <A href="ApacheDOMC++Binding.html" onMouseOut="rolloverOff('side-ext-86');" onMouseOver="rolloverOn('side-ext-86');"><IMG alt="DOM C++ Binding" border="0" height="12" hspace="0" name="side-ext-86" onLoad="rolloverLoad('side-ext-86','graphics/ext-86-label-2.jpg','graphics/ext-86-label-3.jpg');" src="graphics/ext-86-label-3.jpg" vspace="0" width="120"></A><BR>
<A href="migrate.html" onMouseOut="rolloverOff('side-migrate');" onMouseOver="rolloverOn('side-migrate');"><IMG alt="Migration Guide" border="0" height="12" hspace="0" name="side-migrate" onLoad="rolloverLoad('side-migrate','graphics/migrate-label-2.jpg','graphics/migrate-label-3.jpg');" src="graphics/migrate-label-3.jpg" vspace="0" width="120"></A><BR>
Modified: xerces/c/branches/xerces-2.7/doc/install.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/install.xml?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/install.xml (original)
+++ xerces/c/branches/xerces-2.7/doc/install.xml Fri Aug 24 08:57:45 2007
@@ -20,16 +20,29 @@
<s1 title="Installation">
+ <ul>
+ <li><link anchor="Windows">Installation Instructions for Windows</link></li>
+ <li><link anchor="Unix">Installation Instructions for UNIX/Mac OS X/Linux</link></li>
+ <li><link anchor="Cygwin">Installation Instructions for Cygwin</link></li>
+ </ul>
+
+ <anchor name="Windows"/>
+ <s2 title="Windows">
+
+ <p>This section contains installation instructions for the Windows
+ platform.</p>
- <s2 title="Windows NT/2000">
<s3 title="Source distribution">
- <p>The &XercesCName; source is available in the source distribution.
- </p>
+ <p>The &XercesCName; source is available in the source distribution:
+ &XercesCSrcInstallDir;.zip.</p>
+
<p>Install the &XercesCName; source distribution by using <code>unzip</code>
on the &XercesCSrcInstallDir;.zip archive in the Windows environment. You can
- use WinZip, or any other UnZip utility.</p>
-<source>unzip &XercesCSrcInstallDir;.zip</source>
- <p>This creates a '&XercesCSrcInstallDir;' sub-directory
+ use WinZip, or any other UnZip utility:</p>
+<source>
+unzip &XercesCSrcInstallDir;.zip
+</source>
+ <p>This creates the '&XercesCSrcInstallDir;' sub-directory
containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
@@ -38,151 +51,168 @@
</s3>
<s3 title="Binary distribution">
<p>Install the &XercesCName; binary distribution by using <code>unzip</code>
- on the &XercesCInstallDir;-win32.zip archive in the Windows environment. You can
- use WinZip, or any other UnZip utility.</p>
-<source>unzip &XercesCInstallDir;-win32.zip</source>
- <p>This creates a '&XercesCInstallDir;-win32' sub-directory
- containing the &XercesCName; binary distribution. </p>
-
- <p>You need to add the '&XercesCInstallDir;-win32\bin'
- directory to your path: </p>
-
- <p>To do this under Windows NT, go to the start menu, click the
- settings menu and select control panel. When the control panel opens,
- double click on System and select the 'Environment' tab.
- Locate the PATH variable under system variables
- and add <full_path_to_&XercesCInstallDir;>\bin to the PATH variable.
- To do this under Windows 2000 add this line to your AUTOEXEC.BAT file:</p>
-<source>SET PATH=<full_path_to_&XercesCInstallDir;>\bin;%PATH%</source>
- <p>or run the <code>SET PATH</code> command in your shell window.</p>
-
- <p>Besides, if the parser is built with icu message loader (like IBM XML4C binaries),
- or message catalog loader, then you need to create a new environment variable, XERCESC_NLS_HOME
- to point to the directory, $XERCESCROOT/msg, where the message files reside.</p>
-<source>SET XERCESC_NLS_HOME=<full_path_to_&XercesCInstallDir;>\msg</source>
-
- <p>The binary distribution has the built parser library and some samples executables.
- Please refer to the <jump href="samples.html">Samples</jump> for how to run the samples.</p>
+ on the &XercesCInstallDir;-{arch}-windows-{compiler}.zip archive in
+ the Windows environment. Here {arch} denotes the CPU architecture
+ and {compiler} denotes the C++ compiler of your choice. You can use
+ WinZip, or any other UnZip utility. For example:</p>
+
+<source>
+unzip &XercesCInstallDir;-x86-windows-vc_8_0.zip
+</source>
+
+ <p>This creates a '&XercesCInstallDir;-x86-windows-vc_8_0'
+ sub-directory containing the &XercesCName; binary distribution.</p>
+
+ <p>You need to add the '&XercesCInstallDir;-{arch}-windows-{compiler}\bin'
+ directory to your path.
+ To do this go to the start menu, click the settings menu and
+ select control panel. When the control panel opens, double
+ click on System and select the 'Environment' tab.
+ Locate the PATH variable under system variables and add
+ <full-path-to-&XercesCInstallDir;-{arch}-windows-{compiler}>\bin
+ to the PATH variable.</p>
+
+ <p>The binary distribution contains the pre-built parser libraries
+ and sample executables. Please refer to the
+ <jump href="samples.html">Samples</jump> for how to run the
+ samples.</p>
</s3>
</s2>
+ <anchor name="Unix"/>
<s2 title="UNIX">
+
+ <p>This section contains installation instructions for the UNIX,
+ Linux, and Mac OS X platforms.</p>
+
<s3 title="Source distribution">
- <p>The &XercesCName; source is available in the source distribution.
- </p>
- <p>Install the &XercesCName; source distribution &XercesCSrcInstallDir;.tar.gz by extracting the files
- from the compressed archive.</p>
+ <p>The &XercesCName; source is available in the source distribution:
+ &XercesCSrcInstallDir;.tar.gz.</p>
+
+ <p>Install the &XercesCName; source distribution
+ &XercesCSrcInstallDir;.tar.gz by extracting the files
+ from the compressed archive:</p>
<source>
-gunzip &XercesCSrcInstallDir;.tar.gz
-tar &XercesCSrcInstallDir;.tar
+gzip -d &XercesCSrcInstallDir;.tar.gz
+tar -xf &XercesCSrcInstallDir;.tar
</source>
- <p>This creates a '&XercesCSrcInstallDir;' sub-directory
- containing the &XercesCName; source distribution. </p>
-
- <note>On Solaris, please use <code>gtar</code> instead of tar. &install-faq-distrib11;</note>
+ <p>This creates the '&XercesCSrcInstallDir;' sub-directory
+ containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
- please follow the <jump href="build.html">Build Instructions</jump>.</p>
+ please follow the <jump href="build.html">Build Instructions</jump>.</p>
</s3>
<s3 title="Binary distribution">
- <p>Install the binary distribution &XercesCInstallDir;-xxx.tar.gz by extracting the files
- from the compressed archive; where 'xxx' is the corresponding UNIX platform.
+ <p>Install the binary distribution &XercesCInstallDir;-{arch}-{os}-{compiler}.tar.gz
+ by extracting the files from the compressed archive. Here {arch}
+ denotes the CPU architecture, {os} denotes the operating system,
+ and {compiler} denotes the C++ compiler of your choice.
For example:</p>
<source>
-gunzip &XercesCInstallDir;-linux.tar.gz
-tar -xvf &XercesCInstallDir;-linux.tar
+gzip -d &XercesCInstallDir;-x86-linux-gcc_3_4.tar.gz
+tar -xf &XercesCInstallDir;-x86-linux-gcc_3_4.tar
</source>
- <p>This will create an '&XercesCInstallDir;-linux' sub-directory
- containing the &XercesCName; binary distribution. </p>
-
- <note>On Solaris, please use <code>gtar</code> instead of tar. &install-faq-distrib11;</note>
+ <p>This will create an '&XercesCInstallDir;-x86-linux-gcc_3_4'
+ sub-directory containing the &XercesCName; binary distribution.</p>
<p>You will need to add the
- &XercesCInstallDir;-linux/bin directory to your PATH environment variable:</p>
+ &XercesCInstallDir;-{arch}-{os}-{compiler}/bin directory to your
+ PATH environment variable:</p>
<p>For Bourne Shell, K Shell or Bash, type: </p>
-<source>export PATH="$PATH:$HOME/&XercesCInstallDir;-linux/bin"</source>
+<source>
+export PATH="$PATH:<full-path-to-&XercesCInstallDir;-{arch}-{os}-{compiler}>/bin"
+</source>
<p>For C Shell, type:</p>
-<source>setenv PATH "$PATH:$HOME/&XercesCInstallDir;-linux/bin"</source>
+<source>
+setenv PATH "$PATH:<full-path-to-&XercesCInstallDir;-{arch}-{os}-{compiler}>/bin"
+</source>
<p>If you wish to make this setting permanent, you need to change
- your profile by changing your setup files which can be either .profile or .kshrc.</p>
+ your profile by changing your setup files which can be either
+ .profile or .kshrc.</p>
<p>In addition, you will also need to set the library search path.
- (LIBPATH on AIX, LD_LIBRARY_PATH on Solaris and Linux, SHLIB_PATH on HP-UX,
- and DYLD_LIBRARY_PATH on Mac OS X).</p>
+ (LIBPATH on AIX, LD_LIBRARY_PATH on Solaris and Linux,
+ SHLIB_PATH on HP-UX, and DYLD_LIBRARY_PATH on Mac OS X).</p>
- <p>For Bourne Shell, K Shell or Bash, type:</p>
-<source>
-export LIBPATH=$XERCESCROOT/lib:$LIBPATH (on AIX)
-export LD_LIBRARY_PATH=$XERCESCROOT/lib:$LD_LIBRARY_PATH (on Solaris, Linux)
-export SHLIB_PATH=$XERCESCROOT/lib:$SHLIB_PATH (on HP-UX)
-export DYLD_LIBRARY_PATH=$XERCESCROOT/lib:$DYLD_LIBRARY_PATH (on Mac OS X)</source>
+ <p>In the following shell commands, the <xerces-path>
+ denotes the full path to the
+ &XercesCInstallDir;-{arch}-{os}-{compiler} directory. For
+ Bourne Shell, K Shell or Bash, type:</p>
+<source>
+export LIBPATH=<xerces-path>/lib:$LIBPATH (AIX)
+export LD_LIBRARY_PATH=<xerces-path>/lib:$LD_LIBRARY_PATH (Solaris, Linux)
+export SHLIB_PATH=<xerces-path>/lib:$SHLIB_PATH (HP-UX)
+export DYLD_LIBRARY_PATH=<xerces-path>/lib:$DYLD_LIBRARY_PATH (Mac OS X)
+</source>
<p>For C Shell, type:</p>
<source>
-setenv LIBPATH "$XERCESCROOT/lib:$LIBPATH" (on AIX)
-setenv LD_LIBRARY_PATH "$XERCESCROOT/lib:$LD_LIBRARY_PATH" (on Solaris, Linux)
-setenv SHLIB_PATH "$XERCESCROOT/lib:$SHLIB_PATH" (on HP-UX)
-setenv DYLD_LIBRARY_PATH "$XERCESCROOT/lib:$DYLD_LIBRARY_PATH" (Mac OS X)</source>
-
- <p>Besides, if the parser is built with icu message loader (like IBM XML4C binaries),
- or message catalog loader, then you need to create a new environment variable, XERCESC_NLS_HOME
- to point to the directory, $XERCESCROOT/msg, where the message files reside.</p>
-<source>
-export XERCESC_NLS_HOME=$XERCESCROOT/msg
-or
-setenv XERCESC_NLS_HOME=$XERCESCROOT/msg
-</source>
-
- <p>The binary distribution has the built parser library and some samples executables.
- Please refer to the <jump href="samples.html">Samples</jump> for how to run the samples.</p>
+setenv LIBPATH "<xerces-path>/lib:$LIBPATH" (AIX)
+setenv LD_LIBRARY_PATH "<xerces-path>/lib:$LD_LIBRARY_PATH" (Solaris, Linux)
+setenv SHLIB_PATH "<xerces-path>/lib:$SHLIB_PATH" (HP-UX)
+setenv DYLD_LIBRARY_PATH "<xerces-path>/lib:$DYLD_LIBRARY_PATH" (Mac OS X)
+</source>
+ <p>The binary distribution contains the pre-built parser libraries
+ and sample executables. Please refer to the
+ <jump href="samples.html">Samples</jump> for how to run the
+ samples.</p>
</s3>
</s2>
+ <anchor name="Cygwin"/>
<s2 title="Cygwin">
+
+ <p>This section contains installation instructions for the Cygwin
+ platform.</p>
+
<s3 title="Source distribution">
- <p>The &XercesCName; source is available in the source distribution.
- </p>
- <p>Install the &XercesCName; source distribution &XercesCSrcInstallDir;.tar.gz by extracting the files
- from the compressed archive.</p>
+ <p>The &XercesCName; source is available in the source distribution:
+ &XercesCSrcInstallDir;.tar.gz.</p>
+
+ <p>Install the &XercesCName; source distribution
+ &XercesCSrcInstallDir;.tar.gz by extracting the files
+ from the compressed archive:</p>
<source>
-tar -xvzf &XercesCSrcInstallDir;.tar.gz
+tar -xfz &XercesCSrcInstallDir;.tar.gz
</source>
- <p>This creates a '&XercesCSrcInstallDir;' sub-directory
- containing the &XercesCName; source distribution. </p>
+ <p>This creates the '&XercesCSrcInstallDir;' sub-directory
+ containing the &XercesCName; source distribution. </p>
<p>If you need to build the &XercesCName; source after installation,
- please follow the <jump href="build.html">Build Instructions</jump>.</p>
+ please follow the <jump href="build.html">Build Instructions</jump>.
+ </p>
</s3>
+
<s3 title="Binary distribution">
- <p>Install the binary distribution by running
- <jump href="http://www.cygwin.com">Cygwin</jump> setup.exe.
- When you reach the "Packages" step of the Cygwin Setup wizard,
- expand the "Devel" category, then click in the "New" column next
- to "xerces-c-devel" until it reads "&XercesCVersion;-X".</p>
-
- <p>This will install the necessary libraries and include files
- for the &XercesCName; binary distribution.</p>
-
- <p>If you wish to run programs linked to &XercesCName; that were
- built in the Cygwin environment, you need to add your Cygwin
- "bin" directory to your Windows PATH environment variable.
- In typical Cygwin installations, the bin directory is in the
- Cygwin directory on the drive that windows is installed on.
- For instance, if windows is installed to C:\WINNT\System32,
- Your Cygwin bin directory may be "C:\cygwin\bin".</p>
-
- <p>The binary distribution has the built parser library. Sample
- executables may be available in a future release on the
- Cygwin platform. In the meantime, they may be built from the
- source distribution by following the
- <jump href="build.html">Build Instructions</jump> for
- "Building samples".</p>
+ <p>Install the binary distribution by running
+ <jump href="http://www.cygwin.com">Cygwin</jump> setup.exe.
+ When you reach the "Packages" step of the Cygwin Setup wizard,
+ expand the "Devel" category, then click in the "New" column next
+ to "xerces-c-devel" until it reads "&XercesCVersion;-X".</p>
+
+ <p>This will install the necessary libraries and include files
+ for the &XercesCName; binary distribution.</p>
+
+ <p>If you wish to run programs linked to &XercesCName; that were
+ built in the Cygwin environment, you need to add your Cygwin
+ "bin" directory to your Windows PATH environment variable.
+ In typical Cygwin installations, the bin directory is in the
+ Cygwin directory on the drive that windows is installed on.
+ For instance, if windows is installed to "C:\Windows\System32",
+ Your Cygwin bin directory may be "C:\cygwin\bin".</p>
+
+ <p>The binary distribution contains the pre-built parser libraries.
+ Sample executables may be available in a future release on the
+ Cygwin platform. In the meantime, they may be built from the
+ source distribution by following the
+ <jump href="build.html">Build Instructions</jump> for
+ "Building samples".</p>
</s3>
</s2>
</s1>
Modified: xerces/c/branches/xerces-2.7/doc/migration.xml
URL: http://svn.apache.org/viewvc/xerces/c/branches/xerces-2.7/doc/migration.xml?rev=569428&r1=569427&r2=569428&view=diff
==============================================================================
--- xerces/c/branches/xerces-2.7/doc/migration.xml (original)
+++ xerces/c/branches/xerces-2.7/doc/migration.xml Fri Aug 24 08:57:45 2007
@@ -21,65 +21,59 @@
<s1 title="Migration">
<s2 title="Migration Archive">
- <p>For migration information to &XercesCName; 2.6.0 or earlier,
+ <p>For migration information to &XercesCName; 2.7.0 or earlier,
please refer to <jump href="migrate_archive.html">Migration Archive. </jump></p>
</s2>
- <s2 title="Migrating from &XercesCName; 2.6.0 to &XercesCName; &XercesCVersion;">
+ <s2 title="Migrating from &XercesCName; 2.7.0 to &XercesCName; &XercesCVersion;">
<p>The following section is a discussion of the technical differences between
- &XercesCName; 2.6.0 code base and the &XercesCName; &XercesCVersion;.</p>
+ &XercesCName; 2.7.0 code base and the &XercesCName; &XercesCVersion;.</p>
<p>Topics discussed are:</p>
<ul>
- <li><link anchor="NewFeatures270">New features in &XercesCName; &XercesCVersion;</link></li>
- <li><link anchor="API270">Public API Changes</link></li>
+ <li><link anchor="NewFeatures280">New features in &XercesCName; &XercesCVersion;</link></li>
+ <li><link anchor="API280">Public API Changes</link></li>
<ul>
- <li><link anchor="NewAPI270">New Public API</link></li>
- <li><link anchor="ModifiedAPI270">Modified Public API</link></li>
- <li><link anchor="DeprecatedAPI270">Deprecated/Removed Public API</link></li>
+ <li><link anchor="NewAPI280">New Public API</link></li>
+ <li><link anchor="ModifiedAPI280">Modified Public API</link></li>
+ <li><link anchor="DeprecatedAPI280">Deprecated/Removed Public API</link></li>
</ul>
</ul>
- <anchor name="NewFeatures270"/>
+ <anchor name="NewFeatures280"/>
<s3 title="New features in &XercesCName; &XercesCVersion;">
<ul>
- <li>Feature to not generate XML Schema annotations. That is, not to add them to the grammar. If you don't need annotations you may want to turn on this feature to avoid memory bloat for XML Schemas that use annotations heavily.</li>
- <li>Option to skip regenerating the XML Schema annotations when deserializing a grammar. If you don't need annotations you may want to turn on this option to avoid memory bloat for XML Schemas that use annotations heavily.</li>
- <li>Feature to not perform default entity resolution. When the entityResolver returns NULL, the parser doesnt try to resolve the entity externally.</li>
- <li>Feature to do schema-only validation even if there is a DTD.</li>
+ <li>Exponential growth of memory block (from 16KB to 128KB) that are allocated by the DOM heap.</li>
+ <li>The NODE_CLONED notification is now sent to each node's user data handler when cloning the entire DOMDocument.</li>
+ <li>On Windows extract the registry code page from MIME\Database\Charset\<encoding>\@InternetEncoding instead of MIME\Database\Charset\<encoding>\@Codepage.</li>
+ <li>Allow whitespace-only nodes to be added as children of a DOMDocument.</li>
+ <li>When a node is cloned or imported the type information (PSVI) is also copied.</li>
+ <li>When using SAX2, including XMLReaderFactory to use createXMLReader doesn't include xercesc/parsers/SAX2XMLReaderImpl.hpp anymore. If you need to cast the SAX2XMLReader to SAX2XMLReaderImpl,
+ you need to include this header yourself.</li>
</ul>
</s3>
- <anchor name="API270"/>
+ <anchor name="API280"/>
<s3 title="Public API Changes">
<p>The following lists the public API changes between the &XercesCName;
- 2.6.0; and the &XercesCName; &XercesCVersion; releases
+ 2.7.0; and the &XercesCName; &XercesCVersion; releases
of the parser. </p>
- <anchor name="NewAPI270"/>
+ <anchor name="NewAPI280"/>
<s4 title="New Public API">
<ul>
- <li>XMLString: subString, compareIStringASCII, lowercaseASCII, uppercaseASCII</li>
- <li>RefHash2KeysTableOf: rehashing support</li>
- <li>XMemory: placement new and delete</li>
- <li>SAX2XMLFilter</li>
+ <li>XMLBufferMgr: getBufferCount and getAvailableBufferCount</li>
</ul>
</s4>
- <anchor name="ModifiedAPI270"/>
+ <anchor name="ModifiedAPI280"/>
<s4 title="Modified Public API">
- <ul>
- <li></li>
- </ul>
</s4>
- <anchor name="DeprecatedAPI270"/>
+ <anchor name="DeprecatedAPI280"/>
<s4 title="Deprecated/Removed Public API">
- <ul>
- <li></li>
- </ul>
</s4>
</s3>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org