From 6be84e7f070d983ecc056734e8da5fcc186a5684 Mon Sep 17 00:00:00 2001
From: Alberto Massari <amassari@apache.org>
Date: Fri, 7 Jul 2006 14:45:14 +0000
Subject: [PATCH] Updated build instructions in documentation
git-svn-id: https://svn.apache.org/repos/asf/xerces/c/trunk@419900 13f79535-47bb-0310-9956-ffa450edef68
---
doc/apidocs.xml | 8 +-
doc/build-misc.xml | 33 ++--
doc/build-winunix.xml | 393 ++++++++++++++-------------------------
doc/build.xml | 2 +-
doc/dom3.xml | 6 +-
doc/domcount.xml | 2 +-
doc/faq-build.xml | 67 ++-----
doc/faq-contributing.xml | 17 +-
doc/faq-distrib.xml | 2 +-
doc/faq-other.xml | 4 +-
doc/faq-parse.xml | 29 ++-
doc/install.xml | 3 +-
doc/readme.xml | 14 +-
doc/releases_plan.xml | 2 +-
doc/samples.xml | 34 ----
15 files changed, 200 insertions(+), 416 deletions(-)
diff --git a/doc/apidocs.xml b/doc/apidocs.xml
index dd21e84bf..8870ce677 100644
--- a/doc/apidocs.xml
+++ b/doc/apidocs.xml
@@ -35,12 +35,10 @@
DOM Level 2 Core Specification</jump>, a W3C Recommendation of November 13, 2000</li>
<li><jump href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113/">
DOM Level 2 Traversal and Range Specification</jump>, a W3C Recommendation of November 13, 2000</li>
- <li>Contains a partial implementation of the
- <jump href="http://www.w3.org/TR/2002/WD-DOM-Level-3-Core-20020409/">
+ <li><jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/">
DOM Level 3.0 Core Specification</jump>, and
- <jump href="http://www.w3.org/TR/2002/WD-DOM-Level-3-ASLS-20020409/">
- DOM Level 3.0 Abstract Schemas and Load and Save Specification</jump>
- (W3C Working Draft of 09 April 2002). This implementation is experimental.
+ <jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/">
+ DOM Level 3.0 Load and Save Specification</jump>, a W3C Recommendation of April 7, 2004
See <jump href="dom3.html">DOM Level 3 Support</jump> for details.</li>
</ul>
diff --git a/doc/build-misc.xml b/doc/build-misc.xml
index 420176c07..5c54f4323 100644
--- a/doc/build-misc.xml
+++ b/doc/build-misc.xml
@@ -25,10 +25,10 @@
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
- <jump href="http://oss.software.ibm.com/icu/">ICU libraries</jump> from
+ <jump href="http://ibm.com/software/globalization/icu">ICU libraries</jump> from
<jump href="http://oss.software.ibm.com/developerworks/opensource/">IBM's developerWorks site</jump>
or go to the ICU
- <jump href="http://oss.software.ibm.com/icu/download/index.html">download page</jump>
+ <jump href="http://ibm.com/software/globalization/icu/downloads.jsp">download page</jump>
directly.</p>
<note><em>Important:</em> Please remember that <em>ICU and
@@ -42,7 +42,7 @@
MSDEV GUI environment, and the other is to invoke the compiler from the
command line.</p>
- <p>Using, the GUI environment, requires one to edit the project files.
+ <p>Using the GUI environment requires one to edit the project files.
Here, we will describe only the second option. It involves using the
perl script '<code>packageBinaries.pl</code>'.</p>
@@ -69,7 +69,7 @@
'<code>VCVARS32.BAT</code>' or a similar file. Then at the prompt
enter:</p>
-<source>set XERCESCROOT=x:\&XercesCSrcInstallDir;
+<source>
set ICUROOT=x:\icu
cd x:\&XercesCSrcInstallDir;\scripts
</source>
@@ -94,11 +94,6 @@ perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallD
will build both ICU and &XercesCName;, and copy the files (relevant to the binary
drop) to the target directory.</p>
- <p>If the parser is built with icu message loader (as mentioned above), or message
- catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
- the directory, $XERCESCROOT/msg, where the message files reside.
- </p>
-
<p>For a description of options available, you can enter:</p>
<source>perl packageBinaries.pl</source>
</s3>
@@ -111,21 +106,22 @@ perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallD
should be a new directory '<code>$HOME/icu</code>' which contains all the ICU
source files.</p>
- <p>Build the ICU according to the<jump href="http://oss.software.ibm.com/cvs/icu/~checkout~/icu/readme.html">
+ <p>Build the ICU according to the<jump href="http://dev.icu-project.org/cgi-bin/viewcvs.cgi/icu/readme.html?rev=release-3-4">
ICU Build instruction in ICU Readme</jump>. Then have its dll, <code>libicuuc*</code>
and <code>libicudt*</code> available from your library search path.</p>
<p>Then build the &XercesCName; with ICU. This is similar to building a standalone
&XercesCName; library as instructed in <jump href="build-winunix.html#UNIX">
"Building &XercesCName; on UNIX platforms"</jump>; except that you have to specify
- the transcoder option <code>'-t icu'</code> and/or the message loader option
- <code>'-m icu'</code>. For example:</p>
-<source>runConfigure -plinux -cgcc -xg++ -minmem -nsocket -ticu -rpthread</source>
+ the option <code>'--with-icu=$HOME/icu'</code> together with
+ the transcoder option <code>'--enable-transcoder-icu'</code> and/or the message loader option
+ <code>'--enable-msgloader-icu'</code>. For example:</p>
+<source>./configure --with-icu=$HOME/icu --enable-msgloader-inmemory --enable-netaccessor-socket --enable-transcoder-icu</source>
<p>Or instead of building the ICU and &XercesCName; manually in two steps,
you can use the bundled perl script '<code>packageBinaries.pl</code>' which
will build both of them in one step. For example:</p>
-<source>export XERCESCROOT=$HOME/&XercesCSrcInstallDir;
+<source>
export ICUROOT=$HOME/icu
cd $HOME/&XercesCSrcInstallDir;/scripts
</source>
@@ -142,11 +138,6 @@ perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCIn
perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCInstallDir;-aix -m icu
</source>
- <p>If the parser is built with icu message loader (as mentioned above), or message
- catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
- the directory, $XERCESCROOT/msg, where the message files reside.
- </p>
-
</s3>
</s2>
@@ -265,7 +256,7 @@ rpmbuild -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat
<anchor name="PortInfo"/>
<s2 title="I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?">
<p>All platform dependent code in &XercesCProjectName; has been
- isolated to a couple of files, which should ease the porting
+ isolated in a small number of folders, which should ease the porting
effort. Please refer to <jump href="program-others.html#PortingGuidelines">Porting
Guidelines</jump> for further details.</p>
</s2>
@@ -326,7 +317,7 @@ rpmbuild -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat
solved this same problem before you, by checking the Apache XML
mailing list archives at <jump href="http://marc.theaimsgroup.com/?l=xerces-c-dev">
http://marc.theaimsgroup.com/?l=xerces-c-dev</jump> and the
- <jump href="http://nagoya.apache.org/jira">Jira</jump>
+ <jump href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10510">Jira</jump>
Apache bug database.</p>
</s2>
diff --git a/doc/build-winunix.xml b/doc/build-winunix.xml
index 4cc84e8e4..d29f1c6d1 100644
--- a/doc/build-winunix.xml
+++ b/doc/build-winunix.xml
@@ -33,8 +33,6 @@
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 2002):</p>
-<source>&XercesCSrcInstallDir;\Projects\Win32\VC7\xerces-all\xerces-all.sln</source>
<p>For MSVC Version 7.1 (Visual C++ .NET 2003):</p>
<source>&XercesCSrcInstallDir;\Projects\Win32\VC7.1\xerces-all\xerces-all.sln</source>
<p>For MSVC Version 8.0 (Visual C++ .NET 2005):</p>
@@ -45,7 +43,6 @@
<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
(For MSVC V7.1) &XercesCSrcInstallDir;\Projects\Win32\VC7.1\xerces-all\XercesLib\XercesLib.vcproj
(For MSVC V8) &XercesCSrcInstallDir;\Projects\Win32\VC8\xerces-all\XercesLib\XercesLib.vcproj</source>
<p>You must make sure that you are linking your application with
@@ -140,12 +137,8 @@ nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
<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>
+ <li><code>make -f Xerces-all.mak</code>
+ <br/>to build the dll and tests</li>
</ol>
</s2>
@@ -159,10 +152,7 @@ nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
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>
+ the same instructions as the UNIX platforms.</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
@@ -193,17 +183,7 @@ nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
<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.
- 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
- <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>
+ lot of wasted time and support-related e-mail communication.</p>
<p>Besides having all necessary build tools, you also need to know what
compilers we have tested &XercesCName; on. The following table lists the
@@ -232,16 +212,11 @@ nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
<s3 title="Setting build environment variables">
<p>Before doing the build, you must first set your environment variables
- to pick-up the compiler and also specify where you extracted &XercesCName;
- on your machine.
+ to pick-up the compiler.
While the first one is probably set for you by the system administrator, just
make sure you can invoke the compiler. You may do so by typing the
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>
-
- <p>This should be the full path of the directory where you extracted &XercesCName;.</p>
</s3>
<s3 title="Building &XercesCName; library">
@@ -258,259 +233,162 @@ nmake -f XercesLib.mak "CFG=XercesLib - Win64 Release" CPP=ecl.exe
(called <code>configure</code>) is already in your <code>src/xercesc</code>
directory. If not, type:</p>
-<source>cd $XERCESCROOT/src/xercesc
+<source>cd <full path to &XercesCSrcInstallDir;>
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
- using the default compilers like
+ 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>
- 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
- 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
-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)
- [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: no debug]
- -m <message loader> can be 'inmem', 'icu', 'MsgFile' or
- 'iconv' [default: inmem]
- -n <net accessor> can be 'fileonly', 'libwww', 'socket' or
- 'native' [default: socket]
- -t <transcoder> can be 'icu', 'Iconv400', 'Uniconv390',
- 'IconvFBSD', 'IconvGNU' or 'native'
- [default: native]
- -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>
- -h (get help on the above commands)
-</source>
+ you need to make some decisions about what components you want to
+ build into the library.</p>
+
+ <p>You need to specify one options from each category; not specifying one
+ will instruct <code>configure</code> to pick the best choice available:</p>
+
+
+ <p>Net Accessor (used to read data from HTTP sources):</p>
+ <ol>
+ <li><code>--enable-netaccessor-curl</code> Uses curl</li>
+ <li><code>--enable-netaccessor-libwww</code> Uses W3C's libWWW</li>
+ <li><code>--enable-netaccessor-socket</code> Uses plain BSD sockets</li>
+ <li><code>--enable-netaccessor-cfurl</code> Uses cfurl (Mac-only)</li>
+ <li><code>--enable-netaccessor-winsock</code> Uses WinSock (Windows-only, either Cygwin or MinGW)</li>
+ </ol>
+ <p>Message Loader (used to store the strings of the error messages):</p>
+ <ol>
+ <li><code>--enable-msgloader-inmemory</code> Stores the messages in C++ arrays</li>
+ <li><code>--enable-msgloader-icu</code> Stores the messages using ICU resource bundles</li>
+ <li><code>--enable-msgloader-iconv</code> Stores the messages in a iconv message catalog</li>
+ </ol>
+ <p>Transcoder (used to convert strings between UTF-16 and any other supported encoding):</p>
+ <ol>
+ <li><code>--enable-transcoder-gnuiconv</code> Uses GNU iconv library</li>
+ <li><code>--enable-transcoder-iconv</code> Uses iconv library</li>
+ <li><code>--enable-transcoder-icu</code> Uses ICU library</li>
+ <li><code>--enable-transcoder-macosunicodeconverter</code> Uses MacOS APIs (Mac-only)</li>
+ <li><code>--enable-transcoder-windows</code> Uses Windows APIs (Windows-only, either Cygwin or MinGW)</li>
+ </ol>
+
+ <p>By default <code>configure</code> will build both shared and static libraries;
+ you can use <code>--disable-shared</code> or <code>--disable-static</code> to
+ suppress the version you don't need.</p>
+
+ <p>Thread support is enabled by default too;
+ you can use <code>--disable-threads</code> to remove it.</p>
+
+ <p>If you need to specify a compiler (because more than one is found in the PATH,
+ or because it has been renamed to a non-standard name), you should set the
+ environment variables CXX and CC before invoking <code>configure</code>.<br/>
+ If you need special compiler or linker options, define the environment variables
+ CXXFLAGS and LDFLAGS.</p>
<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>
- <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>
- <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.
- </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>
-
- <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>
+ <anchor name="configure-example"/>
+ <p>The simplest way to build &XercesCName; is as follows:</p>
+
+<source>./configure</source>
+
+ <p>This will instruct <code>configure</code> to find out the platform, the compiler
+ and the libraries installed on the system. If more than one library is available
+ for a category, the most powerful will be chosen (e.g. if ICU is available, it will
+ be chosen over iconv).<br/>
+ So it's recommended to examine the log to check if its choices are the correct ones.</p>
+
<source>
-Generating makefiles with the following options ...
-Platform: linux
-C Compiler: gcc
-C++ Compiler: g++
-Message Loader: inmem
-Net Accessor: socket
-Transcoder: native
-Thread option: pthread
-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 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 whether g++ accepts -g... yes
-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 ANSI C header files... yes
-checking for XMLByte... no
+checking build system type... i686-pc-linux-gnu
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
-
-Having build problems?
-Read instructions at http://xml.apache.org/xerces-c/build.html
-Still cannot resolve it?
-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.
-
-export TRANSCODER="NATIVE"
-export MESSAGELOADER="INMEM"
-export NETACCESSOR="Socket"
-export THREADS="pthread"
-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 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>
-
- <p>So now you see what the wrapper script has actually been doing! It has
- invoked <code>configure</code>
- to create the Makefiles in the individual sub-directories, but in addition
- to that, it has set a few environment variables to correctly configure
- your compiler and compiler flags too.</p>
+[..snip..]
+checking for g++... g++
+[..snip..]
+checking for gcc... gcc
+[..snip..]
+checking for libcurl...
+checking for libwww...
+checking whether we can support the libcurl-based NetAccessor... no
+checking whether we can support the libwww-based NetAccessor... no
+checking whether we can support the sockets-based NetAccessor... yes
+checking for which NetAccessor to use (choices: -socket-)... socket
+checking for icu... /usr/local
+checking iconv.h usability... yes
+checking iconv.h presence... yes
+checking for iconv.h... yes
+checking for wchar.h... (cached) yes
+checking for string.h... (cached) yes
+checking for stdlib.h... (cached) yes
+checking stdio.h usability... yes
+checking stdio.h presence... yes
+checking for stdio.h... yes
+checking ctype.h usability... yes
+checking ctype.h presence... yes
+checking for ctype.h... yes
+checking for locale.h... (cached) yes
+checking errno.h usability... yes
+checking errno.h presence... yes
+checking for errno.h... yes
+checking endian.h usability... yes
+checking endian.h presence... yes
+checking for endian.h... yes
+checking for iconv_open... yes
+checking for iconv_close... yes
+checking for iconv... yes
+checking whether we can support the GNU iconv Transcoder... yes
+checking for wchar.h... (cached) yes
+checking for mblen... (cached) yes
+checking for wcstombs... yes
+checking for mbstowcs... yes
+checking whether we can support the iconv Transcoder... yes
+checking whether we can support the ICU Transcoder... yes
+checking for which Transcoder to use (choices: -gnuiconv- -iconv- -icu-)... icu
+checking whether we support the InMemory MsgLoader... yes
+checking whether we support the ICU MsgLoader... yes
+checking for nl_types.h... (cached) yes
+checking for catopen... yes
+checking for catclose... yes
+checking for catgets... yes
+checking whether we can support the iconv MsgLoader... yes
+checking for which MsgLoader to use (choices: -inmemory- -icu- -iconv-)... icu
+checking for which File Manager to use... POSIX
+checking for which Mutex Manager to use... POSIX
+checking for which AtomicOp Manager to use... POSIX
+checking whether we are using SunPro 5.8 compiler... no
+configure: creating ./config.status
+config.status: creating Makefile
+config.status: creating lib/Makefile
+config.status: creating src/Makefile
+config.status: creating src/xercesc/util/MsgLoaders/ICU/resources/Makefile
+config.status: creating obj/Makefile
+config.status: creating tests/Makefile
+config.status: creating samples/Makefile
+config.status: creating config.h
+config.status: creating src/xercesc/util/Xerces_autoconf_config.hpp
+config.status: executing depfiles commands
+</source>
<p>Now that the Makefiles are all created, you are ready to do the actual build.</p>
<source>gmake</source>
- <p>Is that it? Yes, that's all you need to build &XercesCName;.</p>
- </s3>
+ <p>Is that it? Yes, that's all you need to build &XercesCName; and the associated samples.</p>
- <s3 title="Building samples">
- <p>The installation process for the samples is same on all UNIX
- platforms.
- </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)
-</source>
+ <p>If you need to build the tests, type</p>
+
+<source>gmake check</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 delete all the generated object files and executables, type:</p>
- <p>To delete all the generated object files and executables, type:</p>
<source>gmake clean</source>
+
</s3>
</s2>
- <anchor name="UNIX_SingleThread"/>
+<!-- <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>The following steps guide you to create a single-threaded library for each platform:</p>
<p>For Aix - </p>
<ul>
@@ -551,4 +429,5 @@ Usage: runConfigure "options"
-DXML_USE_DCE</code></li>
</ul>
</s2>
+-->
</s1>
diff --git a/doc/build.xml b/doc/build.xml
index 997584c20..2fe0cc8e0 100644
--- a/doc/build.xml
+++ b/doc/build.xml
@@ -29,7 +29,7 @@
<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#UNIX_SingleThread">Building &XercesCName; as a single-threaded library on Unix platforms</jump></li> -->
</ul>
</s2>
diff --git a/doc/dom3.xml b/doc/dom3.xml
index 4d7236754..9ddcefb6b 100644
--- a/doc/dom3.xml
+++ b/doc/dom3.xml
@@ -39,6 +39,9 @@
<li>
<code>DOMImplementation</code>: createLSParser(MODE_ASYNCHRONOUS)
</li>
+ <li>
+ <code>DOMTypeInfo</code>: isDerivedFrom()
+ </li>
</ul>
</s2>
@@ -51,8 +54,5 @@
</ul>
</s2>
-<s2 title='Implementation of DOM Level 3 Validation'>
- <p>The entire section has not been implemented in &XercesCName; &XercesCVersion;.</p>
-</s2>
</s1>
diff --git a/doc/domcount.xml b/doc/domcount.xml
index 8c97499a1..5c321d0b1 100644
--- a/doc/domcount.xml
+++ b/doc/domcount.xml
@@ -34,7 +34,7 @@
Usage:
DOMCount [options] <XML file | List file>
-This program invokes the DOM parser, builds the DOM tree,
+This program invokes the DOMLSParser, builds the DOM tree,
and then prints the number of elements found in each XML file.
Options:
diff --git a/doc/faq-build.xml b/doc/faq-build.xml
index 8f1b4e9d5..e2c942cd6 100644
--- a/doc/faq-build.xml
+++ b/doc/faq-build.xml
@@ -29,7 +29,7 @@
<p>If C++ Namespace is ENABLED, users' applications must
namespace qualify all the &XercesCName; classes, data, and
- variables with <code>XERCES_CPP_NAMESPACE_QUALIFIER </code>
+ variables with <code>XERCES_CPP_NAMESPACE_QUALIFIER</code>
or add the <code>XERCES_CPP_NAMESPACE_USE</code> clause.
Users also need to ensure all forward declarations are
properly qualified or scoped.
@@ -55,7 +55,7 @@
with the &XercesCName; &XercesCVersion; <code>&XercesCNamespace;::DOMDocument</code>
and thus lead to the compilation errors.</p>
- <p> Qualifier the use of DOMDocument in your application explicitly e.g.
+ <p> Qualifying the use of DOMDocument in your application explicitly e.g.
<br/><br/><code>XERCES_CPP_NAMESPACE_QUALIFIER DOMDocument * fDoc;</code><br/><br/>
will eliminate these compilation problems.
</p>
@@ -63,16 +63,6 @@
</a>
</faq>
- <faq title="Why can't the compiler find the include files?">
-
- <q>Why can't the compiler find the include files?</q>
-
- <a><p>A common cause for this problem is setting build environment
- variable XERCESROOT instead of setting variable XERCESCROOT.
- Note the C before ROOT.</p>
- </a>
- </faq>
-
<faq title="Why do I get Internal Compiler Error when compiling &XercesCName; for a 64bit target with gcc?">
<q>Why do I get Internal Compiler Error when compiling &XercesCName; for a 64bit target with gcc?</q>
<a>
@@ -81,20 +71,6 @@
</faq>
- <faq title="Why do I get compilation error when compiling &XercesCName; on FreeBSD with native transcoder?">
-
- <q>Why do I get compilation error when compiling &XercesCName; on FreeBSD with native transcoder?</q>
-
- <a>
- <p>Please make sure you configure with "-t IconvFBSD" to use FreeBSD specific native transcoder.
- </p>
-
- <p>Or you can use ICU transcoder (configure with -t icu) instead of the native transcoder.
- </p>
-
- </a>
- </faq>
-
<faq title="Building &XercesCName; with compiler GCC 2.7.x or 2.8.x gives problem, what's wrong?">
<q>Building &XercesCName; with compiler GCC 2.7.x or 2.8.x gives problem, what's wrong?</q>
@@ -119,6 +95,8 @@
<p>Please check the following:</p>
<ol>
+ <li>Verify that you have specified the appropriate option and library path in the linker
+ command line</li>
<li>If you're using the binary build of &XercesCName;, make sure that the OS and compiler are
the same version as the ones used to build the binary &faq-build-faq-distrib1;. Different OS and
compiler versions might cause unresolved linking problems or compilation
@@ -201,11 +179,6 @@ export SHLIB_PATH=$SHLIB_PATH:$HOME/fastxmlparser/lib # (HP-UX)</source>
need to put in two additional DLLs. In the Windows build these are <code>icuuc*.dll</code> and <code>icudt*.dll</code> which must be available from your PATH settings. On UNIX, these
libraries are called <code>libicuuc*.so</code> and <code>libicudt*.so</code> (or <code>.sl</code> for HP-UX or <code>.a</code> for AIX) which must be available from your library search path.</p>
- <p>If the parser is built with icu message loader (as mentioned above), or message
- catalog loader, you need an environment variable, XERCESC_NLS_HOME to point to
- the directory, $XERCESCROOT/msg, where the message files reside.
- </p>
-
</a>
</faq>
@@ -280,9 +253,9 @@ export SHLIB_PATH=$SHLIB_PATH:$HOME/fastxmlparser/lib # (HP-UX)</source>
<source>
try {
- XMLPlatformUtils::Initialize();
+ XERCES_CPP_NAMESPACE_QUALIFIER XMLPlatformUtils::Initialize();
}
-catch (const XMLException& toCatch) {
+catch (const XERCES_CPP_NAMESPACE_QUALIFIER XMLException& toCatch) {
// Do your failure processing here
}</source>
@@ -350,7 +323,7 @@ catch (const XMLException& toCatch) {
<li>start debugging (so the debug menu appears)</li>
<li>from the debug menu select "Exceptions"</li>
<li>from the box that opens select "Microsoft C++ Exception" and set it
- to "Stop if not handled" instead of "stop always".</li>
+ to "Stop if not handled" instead of "Stop always".</li>
</ul>
<p>You'll still land in the debugger if your program is terminating
@@ -360,16 +333,6 @@ catch (const XMLException& toCatch) {
</a>
</faq>
- <faq title="Fatal Error: Cannot open include file: XXX: No such file or directory">
- <q>"Fatal Error: Cannot open include file: XXX: No such file or directory"?</q>
- <a>
- <p>
- Due to the recent directory change, you may need to either update your
- project file, makefile, or your source/header file, for details,
- please refer to <jump href="migrate.html#DirChange">Directory Change. </jump></p>
- </a>
- </faq>
-
<faq title="Cannot load message domain, Xerces Panic Error">
<q>"Cannot load message domain, Xerces Panic Error"?</q>
<a>
@@ -377,10 +340,10 @@ catch (const XMLException& toCatch) {
you need to make sure that the message library &faq-build-faq-distrib3;
is located in a directory which is on the library search path.
Or the message resource file, XercesMessages_en_US.res, is in the directory given at the call to
- XMLPlatformUtils::Initialize(), or is located in the directory pointed to by the environment variable
- XERCESC_NLS_HOME, or at $XERCESCROOT/msg.
+ XMLPlatformUtils::Initialize(), or is located in the directory pointed to by the environment
+ variable XERCESC_NLS_HOME, or at $XERCESCROOT/msg.
</p>
- <p>If the parser is built with message catalog loader, you need to make sure that the message
+ <p>If the parser is built with iconv message catalog loader, you need to make sure that the message
catalog file, XercesMessages_en_US.cat, is in the directory given at the call to XMLPlatformUtils::Initialize(),
or is located in the directory pointed to by the environment variable XERCESC_NLS_HOME, or
at $XERCESCROOT/msg.
@@ -420,10 +383,10 @@ catch (const XMLException& toCatch) {
on your system. The application itself, written in Java, is
part of Xerces.</p>
- <p>To regenerate the documentation, go to directory <code>$XERCESCROOT</code>
+ <p>To regenerate the documentation, go to Xerces directory
and start <code>createDocs.sh</code> (for Unix) or
<code>createdocs.bat</code> (for Windows). The result can be
- found in directory <code>$XERCESCROOT/doc/html</code>.</p>
+ found in the subdirectory <code>doc/html</code>.</p>
<p>
To regenerate the API documentation, you need to have at least
@@ -440,12 +403,12 @@ catch (const XMLException& toCatch) {
include it.)</p>
<p>If you do not have GraphViz, or do not want to use it, you
- have to edit file <code>$XERCESCROOT/doc/Doxyfile</code> and change <code>HAVE_DOT =
+ have to edit file <code>doc/Doxyfile</code> and change <code>HAVE_DOT =
YES</code> into <code>HAVE_DOT = NO</code>.</p>
<p>To actually regenerate the API documentation, go to directory
- <code>$XERCESCROOT/doc/</code> and start Doxygen. The result can be
- found in directory <code>$XERCESCROOT/doc/html/apiDocs</code>.</p>
+ <code>doc/</code> and start Doxygen. The result can be
+ found in directory <code>doc/html/apiDocs</code>.</p>
</a>
</faq>
diff --git a/doc/faq-contributing.xml b/doc/faq-contributing.xml
index 719a55144..e85e92f51 100644
--- a/doc/faq-contributing.xml
+++ b/doc/faq-contributing.xml
@@ -31,7 +31,7 @@
<ol>
<li>Check out and build the most recent Xerces code. For
instructions on how to do this, see <jump
- href="http://xml.apache.org/cvs.html">Apache XML Project CVS
+ href="http://xml.apache.org/svn.html">Apache XML Project Subversion
Information</jump>. If you do this, you can confirm that your
bug still exists and has not been fixed since the last
release.
@@ -46,8 +46,8 @@
<li>
Prepare a patch to fix Xerces code. To do this, when you
have applied your changes to a local copy of the most
- recent xerces source code, do <code>cvs diff -u
- file</code> for each file you've changed.
+ recent xerces source code, do <code>svn diff file</code>
+ for each file you've changed.
Keep in mind the coding guidelines for &XercesCName; as
described below.
</li>
@@ -57,7 +57,7 @@
apply.
</li>
<li>
- Submit a bug report on <jump href="http://nagoya.apache.org/jira">Jira</jump>,
+ Submit a bug report on <jump href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10510">Jira</jump>,
the Apache bug database. Pick the product "Xerces-C++"
(remembering to attach your patches and test code)
or, if you think your patch might need some discussion,
@@ -188,18 +188,13 @@
<ol>
<li>Update the release information in the following files:<br/>
- <code>Projects/Win32/VC6/xerces-all/XercesLib/XercesDeprecatedDOMLib.dsp</code>
- <code>Projects/Win32/VC6/xerces-all/XercesLib/XercesDeprecatedDOMLib.mak</code>
<code>Projects/Win32/VC6/xerces-all/XercesLib/XercesLib.dsp</code>
<code>Projects/Win32/VC6/xerces-all/XercesLib/XercesLib.mak</code>
<code>Projects/Win32/VC6/xerces-all/xerces-com/xerces-com.dsp</code>
- <code>Projects/Win32/VC7.1/xerces-all/XercesLib/XercesDeprecatedDOMLib.vcproj</code>
<code>Projects/Win32/VC7.1/xerces-all/XercesLib/XercesLib.vcproj</code>
<code>Projects/Win32/VC7.1/xerces-all/xerces-com/xerces-com.vcproj</code>
- <br/>
- <code>Projects/Win32/VC7/xerces-all/XercesLib/XercesDeprecatedDOMLib.vcproj</code>
- <code>Projects/Win32/VC7/xerces-all/XercesLib/XercesLib.vcproj</code>
- <code>Projects/Win32/VC7/xerces-all/xerces-com/xerces-com.vcproj</code>
+ <code>Projects/Win32/VC8/xerces-all/XercesLib/XercesLib.vcproj</code>
+ <code>Projects/Win32/VC8/xerces-all/xerces-com/xerces-com.vcproj</code>
<br/>
<code>Projects/MacOS/Xcode/XercesLib/Info-XercesLib.plist</code>
<code>scripts/packageBinaries.pl</code>
diff --git a/doc/faq-distrib.xml b/doc/faq-distrib.xml
index 790b354b0..5e3ea244d 100644
--- a/doc/faq-distrib.xml
+++ b/doc/faq-distrib.xml
@@ -46,7 +46,7 @@
encodings, say in Shift-JIS, Big5 etc., then you cannot
use Xerces-C. XML4C addresses this need. It combines Xerces-C
and <jump
- href="http://oss.software.ibm.com/icu/">
+ href="http://ibm.com/software/globalization/icu/">
International Components for Unicode (ICU)</jump> and
provides support for over 100 different encodings.
XML4C also uses ICU Resource Bundle to load the messages.
diff --git a/doc/faq-other.xml b/doc/faq-other.xml
index 9bd801bfd..d1a039d9a 100644
--- a/doc/faq-other.xml
+++ b/doc/faq-other.xml
@@ -84,8 +84,8 @@ SUCH DAMAGE.</source>
<p>Yes. The Xerces family of products also has a Java version. More
information is available at:
- <jump href="http://xml.apache.org/xerces2-j/index.html">
- http://xml.apache.org/xerces2-j/index.html</jump></p>
+ <jump href="http://xerces.apache.org/xerces2-j">
+ http://xerces.apache.org/xerces2-j</jump></p>
</a>
</faq>
diff --git a/doc/faq-parse.xml b/doc/faq-parse.xml
index 8a56825f7..b6fa8dab4 100644
--- a/doc/faq-parse.xml
+++ b/doc/faq-parse.xml
@@ -74,9 +74,9 @@
<source>
try {
- XMLPlatformUtils::Initialize();
+ XERCES_CPP_NAMESPACE_QUALIFIER XMLPlatformUtils::Initialize();
}
-catch (const XMLException& toCatch) {
+catch (const XERCES_CPP_NAMESPACE_QUALIFIER XMLException& toCatch) {
// Do your failure processing here
}</source>
@@ -203,13 +203,13 @@ catch (const XMLException& toCatch) {
<source>
1: {
2: XMLPlatformUtils::Initialize();
-3: DOMString c("hello");
+3: XercesDOMParser parser;
4: XMLPlatformUtils::Terminate();
5: }
</source>
- <p>The DOMString object "c" is destructed when going out of scope at line 5 before the closing
- brace. As a result, DOMString destructor is called at line 5 after
+ <p>The XercesDOMParser object "parser" is destructed when going out of scope at line 5 before the closing
+ brace. As a result, XercesDOMParser destructor is called at line 5 after
XMLPlatformUtils::Terminate() which is wrong. Correct code should be:
</p>
@@ -217,7 +217,7 @@ catch (const XMLException& toCatch) {
1: {
2: XMLPlatformUtils::Initialize();
2a: {
-3: DOMString c("hello");
+3: XercesDOMParser parser;
3a: }
4: XMLPlatformUtils::Terminate();
5: }
@@ -320,11 +320,6 @@ void myParsingFunction()
instances may be concurrently accessed from different threads, but any given
document instance can only be accessed by one thread at a time.</p>
- <p>DOMStrings allow multiple concurrent readers. All DOMString const
- methods are thread safe, and can be concurrently entered by multiple threads.
- Non-const DOMString methods, such as <code>appendData()</code>, are not thread safe and the application must guarantee that no other
- methods (including const methods) are executed concurrently with them.</p>
-
<p>The application also needs to guarantee that only one thread has entered either the
method XMLPlatformUtils::Initialize() or the method XMLPlatformUtils::Terminate() at any
one time.</p>
@@ -353,7 +348,7 @@ void myParsingFunction()
</p>
<p>If you are using XML4C where ICU is used, you may call ICU function u_cleanup() to clean up
- ICU static data. Please see <jump href="http://oss.software.ibm.com/icu/">ICU documentation</jump>
+ ICU static data. Please see <jump href="http://ibm.com/software/globalization/icu/">ICU documentation</jump>
for details.
</p>
</a>
@@ -379,7 +374,7 @@ void myParsingFunction()
</p>
<p>If you are using XML4C where ICU is used, you may call ICU function u_cleanup() to clean up
- ICU static data. Please see <jump href="http://oss.software.ibm.com/icu/">ICU documentation</jump>
+ ICU static data. Please see <jump href="http://ibm.com/software/globalization/icu/">ICU documentation</jump>
for details.
</p>
</a>
@@ -443,7 +438,7 @@ void myParsingFunction()
<q>Why does DOMNode::cloneNode() not clone the pointer assigned to a DOMNode via DOMNode::setUserData()?</q>
<a>
<p>&XercesCName; supports the DOMNode::userData specified
- in <jump href="http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030226/DOM3-Core.html#core-ID-3A0ED0A4">
+ in <jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-3A0ED0A4">
the DOM level 3 Node interface</jump>. As
is made clear in the description of the behaviour of
<code>cloneNode()</code>, userData that has been set on the
@@ -509,7 +504,9 @@ void myParsingFunction()
platforms.</p>
<p>To address the need to make remote connections to resources specified
- using additional protocols, ftp for example, &XercesCName; provides the <code>NetAccessor</code> interface. The header file is <code>src/xercesc/util/XMLNetAccessor.hpp</code>. This interface allows you to plug in your own implementation of URL
+ using additional protocols, ftp for example, &XercesCName; provides the <code>NetAccessor</code> interface.
+ The header file is <code>src/xercesc/util/XMLNetAccessor.hpp</code>.
+ This interface allows you to plug in your own implementation of URL
networking code into the &XercesCName; parser.</p>
</a>
@@ -569,7 +566,7 @@ void myParsingFunction()
parse input XML files in these above mentioned encodings.</p>
<p>XML4C -- the version of Xerces-C available from IBM -- combines Xerces-C
- and <jump href="http://oss.software.ibm.com/icu/">
+ and <jump href="http://ibm.com/software/globalization/icu/">
International Components for Unicode (ICU)</jump> and
extends the encoding support to over 100 different encodings that are allowed
by ICU. In particular, all the encodings registered with the
diff --git a/doc/install.xml b/doc/install.xml
index d3211173d..c1b711bb8 100644
--- a/doc/install.xml
+++ b/doc/install.xml
@@ -180,8 +180,7 @@ tar -xvzf &XercesCSrcInstallDir;.tar.gz
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>
+ <jump href="build.html">Build Instructions</jump>.</p>
</s3>
</s2>
</s1>
diff --git a/doc/readme.xml b/doc/readme.xml
index 2b67fe280..68ede4530 100644
--- a/doc/readme.xml
+++ b/doc/readme.xml
@@ -77,16 +77,12 @@
XML Schema Part 1: Structure</jump>, W3C Recommendation 2 May 2001</li>
<li><jump href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">
XML Schema Part 2: Datatypes</jump>, W3C Recommendation 2 May 2001</li>
+ <li><jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407">
+ DOM Level 3.0 Core Specification</jump>, W3C Recommendation 7 April 2004</li>
+ <li><jump href="http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407">
+ DOM Level 3.0 Load and Save Specification</jump>, W3C Recommendation 7 April 2004<br/>
+ See <jump href="dom3.html">DOM Level 3 Support</jump> for detail.</li>
</ul>
- <li>Contains a partial implementation of the
- <jump href="http://www.w3.org/TR/DOM-Level-3-Core/">
- DOM Level 3.0 Core Specification</jump>, Version 1.0 W3C Working Draft 26 February 2003
- and
- <jump href="http://www.w3.org/TR/DOM-Level-3-LS/">
- Document Object Model (DOM) Level 3 Load and Save Specification</jump>,
- Version 1.0 W3C Working Draft 26 February 2003.
- This implementation is experimental.
- See <jump href="dom3.html">DOM Level 3 Support</jump> for detail.</li>
<li>Source code, samples, and documentation is provided</li>
<li>Programmatic generation and validation of XML</li>
<li>Pluggable catalogs, validators and encodings</li>
diff --git a/doc/releases_plan.xml b/doc/releases_plan.xml
index 7b7602ba9..86e524038 100644
--- a/doc/releases_plan.xml
+++ b/doc/releases_plan.xml
@@ -22,7 +22,7 @@
<s2 title="&XercesCName; Future Releases Plan">
<p>This document highlights the release plan for &XercesCName;.</p>
-<s3 title="Current Status"><p>&XercesCName; 2.6.0 - released on September 29, 2004.</p></s3>
+<s3 title="Current Status"><p>&XercesCName; 2.7.0 - released on September 1, 2005.</p></s3>
<s3 title="Next Target Release">
<p>The &XercesCName; team is currently working on plans for future releases.
diff --git a/doc/samples.xml b/doc/samples.xml
index 4bc52c947..7fa6c36c3 100644
--- a/doc/samples.xml
+++ b/doc/samples.xml
@@ -26,40 +26,6 @@
the parser. Sample XML data files are provided in the samples/data directory.</p>
</s2>
- <s2 title="Building the Samples">
- <p>For general information related to building--including
- platform-specific information--please refer to the
- <jump href="build.html">Build Page</jump>. This
- information covers a standard installation where one
- has downloaded the entire Xerces-C binary distribution
- to a place on the filesystem to which one has write
- access. Below, we cover what to do if Xerces-C has been
- preinstalled on a system into a directory to which one
- does not have write access, but compiling the samples is
- desired.</p>
- <p>
- In this situation, just do the following:
- </p>
- <ol>
- <li>Copy the entire contents of the
- <code>samples</code> directory into a directory named
- samples that you have write-access to;</li>
- <li>Set the <code>XERCESCOUT</code> environment
- variable to point to the directory that is the parent
- of the newly-created <code>samples</code>
- directory;</li>
- <li>Proceed as normal to compile the samples (not
- forgetting to set <code>XERCESCROOT</code> to point
- to the place on the file system where Xerces-C's
- include files etc. are to be found);</li>
- </ol>
- <p>Once this is done, the compiled samples will be placed
- in a directory named <code>bin</code>; this directory
- will be located in the same directory as the
- <code>samples</code> directory created in step 1
- above.</p>
- </s2>
-
<s2 title="Running the Samples">
<p>The sample applications are dependent on the &XercesCName; shared library
--
GitLab