You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by bo...@apache.org on 2008/02/25 16:35:11 UTC
svn commit: r630879 [1/4] - in /xerces/c/trunk/doc: ./ html/ html/apiDocs-3/
html/apiDocs/ style/dtd/ style/graphics/ style/resources/ style/stylesheets/
Author: borisk
Date: Mon Feb 25 07:35:02 2008
New Revision: 630879
URL: http://svn.apache.org/viewvc?rev=630879&view=rev
Log:
Factor-out project-independent pages into a separate project (web). Change the documentation to allow simultaneous hosting of several releases on the website.
Added:
xerces/c/trunk/doc/html/apiDocs-3/
- copied from r630224, xerces/c/trunk/doc/html/apiDocs/
xerces/c/trunk/doc/style/graphics/section.gif (with props)
xerces/c/trunk/doc/style/resources/separator-space.gif (with props)
xerces/c/trunk/doc/style/stylesheets/context2section.xsl
Removed:
xerces/c/trunk/doc/blueb.gif
xerces/c/trunk/doc/bug-report.xml
xerces/c/trunk/doc/charter.xml
xerces/c/trunk/doc/feedback.xml
xerces/c/trunk/doc/html/apiDocs/
xerces/c/trunk/doc/html/download.cgi
xerces/c/trunk/doc/html/download.html
xerces/c/trunk/doc/index.html
xerces/c/trunk/doc/pdf-c.xml
xerces/c/trunk/doc/releases.xml
xerces/c/trunk/doc/releases_archive.xml
xerces/c/trunk/doc/releases_plan.xml
Modified:
xerces/c/trunk/doc/Doxyfile
xerces/c/trunk/doc/apidocs.xml
xerces/c/trunk/doc/build-misc.xml
xerces/c/trunk/doc/build-other.xml
xerces/c/trunk/doc/build-winunix.xml
xerces/c/trunk/doc/build.xml
xerces/c/trunk/doc/dom3.xml
xerces/c/trunk/doc/domcount.xml
xerces/c/trunk/doc/domprint.xml
xerces/c/trunk/doc/enumval.xml
xerces/c/trunk/doc/faq-build.xml
xerces/c/trunk/doc/faq-contributing.xml
xerces/c/trunk/doc/faq-distrib.xml
xerces/c/trunk/doc/faq-other.xml
xerces/c/trunk/doc/faq-parse.xml
xerces/c/trunk/doc/install.xml
xerces/c/trunk/doc/migration.xml
xerces/c/trunk/doc/migration_archive.xml
xerces/c/trunk/doc/pparse.xml
xerces/c/trunk/doc/program-dom.xml
xerces/c/trunk/doc/program-others.xml
xerces/c/trunk/doc/program-sax.xml
xerces/c/trunk/doc/program-sax2.xml
xerces/c/trunk/doc/program.xml
xerces/c/trunk/doc/psviwriter.xml
xerces/c/trunk/doc/readme.xml
xerces/c/trunk/doc/redirect.xml
xerces/c/trunk/doc/samples.xml
xerces/c/trunk/doc/sax2count.xml
xerces/c/trunk/doc/sax2print.xml
xerces/c/trunk/doc/saxcount.xml
xerces/c/trunk/doc/saxprint.xml
xerces/c/trunk/doc/schema.xml
xerces/c/trunk/doc/scmprint.xml
xerces/c/trunk/doc/senumval.xml
xerces/c/trunk/doc/stdinparse.xml
xerces/c/trunk/doc/style/dtd/book.dtd
xerces/c/trunk/doc/style/dtd/entities.ent
xerces/c/trunk/doc/style/stylesheets/book2project.xsl
xerces/c/trunk/doc/style/stylesheets/document2html.xsl
xerces/c/trunk/doc/xerces-c_book.xml
Modified: xerces/c/trunk/doc/Doxyfile
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/Doxyfile?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/Doxyfile (original)
+++ xerces/c/trunk/doc/Doxyfile Mon Feb 25 07:35:02 2008
@@ -585,7 +585,7 @@
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.
-HTML_OUTPUT = apiDocs
+HTML_OUTPUT = apiDocs-3
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
Modified: xerces/c/trunk/doc/apidocs.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/apidocs.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/apidocs.xml (original)
+++ xerces/c/trunk/doc/apidocs.xml Mon Feb 25 07:35:02 2008
@@ -40,13 +40,13 @@
DOM Level 3.0 Core Specification</jump>, and
<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>
+ See <jump href="dom3-&XercesC3Series;.html">DOM Level 3 Support</jump> for details.</li>
</ul>
<p>For a complete understanding of how the &XercesCName; APIs work,
we recommend you to read these documents.</p>
- <p>See the <em><jump href="apiDocs/index.html">&XercesCName; API documentation</jump></em> for more details.</p>
+ <p>See the <em><jump href="apiDocs-&XercesC3Series;/index.html">&XercesCName; API documentation</jump></em> for more details.</p>
<note>The API documentation is automatically generated using
<jump href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</jump> and
Modified: xerces/c/trunk/doc/build-misc.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/build-misc.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/build-misc.xml (original)
+++ xerces/c/trunk/doc/build-misc.xml Mon Feb 25 07:35:02 2008
@@ -22,15 +22,11 @@
<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
- <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://ibm.com/software/globalization/icu/downloads.jsp">download page</jump>
- directly.</p>
+ IBM. You can get ICU libraries from
+ <jump href="http://icu-project.org/">ICU project site</jump>.</p>
<note><em>Important:</em> Please remember that <em>ICU and
&XercesCName; must be built with the same compiler</em>,
@@ -43,7 +39,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>
@@ -56,7 +52,7 @@
<p>Extract &XercesCName; source files from the .zip archive using WinZip, say
in the root directory (an arbitrary drive x:). It should create a directory like
- '<code>x:\&XercesCSrcInstallDir;</code>'.</p>
+ '<code>x:\&XercesC3SrcInstallDir;</code>'.</p>
<p>Extract the ICU files, using WinZip, in root directory of the disk
where you have installed &XercesCName;, sources. After extraction, there
@@ -72,19 +68,19 @@
<source>
set ICUROOT=x:\icu
-cd x:\&XercesCSrcInstallDir;\scripts
+cd x:\&XercesC3SrcInstallDir;\scripts
</source>
<p>To build with ICU, either specify using ICU transcoding service,</p>
<source>
-perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallDir;-win32 -t icu
+perl packageBinaries.pl -s x:\&XercesC3SrcInstallDir; -o x:\temp\&XercesC3InstallDir;-win32 -t icu
</source>
<p> or specify using ICU message loader service</p>
<source>
-perl packageBinaries.pl -s x:\&XercesCSrcInstallDir; -o x:\temp\&XercesCInstallDir;-win32 -m icu
+perl packageBinaries.pl -s x:\&XercesC3SrcInstallDir; -o x:\temp\&XercesC3InstallDir;-win32 -m icu
</source>
<p>(Match the source directory to your system; the target directory can be
@@ -100,45 +96,50 @@
</s3>
<s3 title="Building on UNIX">
<p>Extract &XercesCName; source files into, say, the home directory ($HOME).
- It should create a directory like '<code>$HOME/&XercesCSrcInstallDir;</code>'.</p>
+ It should create a directory like '<code>$HOME/&XercesC3SrcInstallDir;</code>'.</p>
<p>Extract the ICU files into the same directory
where you have installed &XercesCName; sources. After extraction, there
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://dev.icu-project.org/cgi-bin/viewcvs.cgi/icu/readme.html?rev=release-3-4">
+ <p>Build the ICU according to the<jump href="http://icu-project.org/">
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">
+ &XercesCName; library as instructed in <jump href="build-winunix-&XercesC3Series;.html#UNIX">
"Building &XercesCName; on UNIX platforms"</jump>; except that you have to specify
- the option <code>'--with-icu=$HOME/icu'</code> together with
+ 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>
+ <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 ICUROOT=$HOME/icu
-cd $HOME/&XercesCSrcInstallDir;/scripts
+cd $HOME/&XercesC3SrcInstallDir;/scripts
</source>
<p>To build with ICU, either specify using ICU transcoding service,</p>
<source>
-perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCInstallDir;-aix -t icu
+perl packageBinaries.pl -s $HOME/&XercesC3SrcInstallDir; -o $HOME/temp/&XercesC3InstallDir;-aix -t icu
</source>
<p> or specify using ICU message loader service</p>
<source>
-perl packageBinaries.pl -s $HOME/&XercesCSrcInstallDir; -o $HOME/temp/&XercesCInstallDir;-aix -m icu
+perl packageBinaries.pl -s $HOME/&XercesC3SrcInstallDir; -o $HOME/temp/&XercesC3InstallDir;-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>
@@ -147,74 +148,16 @@
<p>&XercesCName; may be built from the distributed source archive directly on Linux
using RPM. For example: </p>
<source>
-rpm -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.0 and older)
+rpm -ta &XercesC3SrcInstallDir;.tar.gz (rpm 4.0 and older)
or
-rpmbuild -ta &XercesCSrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat 8)
+rpmbuild -ta &XercesC3SrcInstallDir;.tar.gz (rpm 4.1 and later; ships with RedHat 8)
</source>
<p>The &XercesCName; RPM specification can be found in
- <br/><code>&XercesCSrcInstallDir;/xerces-c.spec</code>.</p>
+ <br/><code>&XercesC3SrcInstallDir;/xerces-c.spec</code>.</p>
<p>Please refer to the <jump href="http://www.rpm.org/RPM-HOWTO">RPM-HOWTO</jump>,
for more RPM related information.</p>
</s2>
- <anchor name="WinCOM"/>
- <s2 title="Building &XercesCName; COM Wrapper on Windows">
- <p>To build the COM module for use with XML on Windows platforms, you
- must first set up your machine appropriately with necessary tools and
- software modules and then try to compile it. The end result is an additional
- library that you can use along with the standard &XercesCName; for writing
- VB templates or for use with IE 5.0 using JavaScript.</p>
-
- <s3 title="Setting up your machine for COM">
- <p>To build the COM project you will need to install the MS PlatformSDK.
- Some of the header files we use don't come with Visual C++ 6.0. You may
- download it from Microsoft's Website at <jump href="http://www.microsoft.com/msdownload/platformsdk/setuplauncher.htm">http://www.microsoft.com/msdownload/platformsdk/setuplauncher.htm</jump>
- or directly FTP it from <jump href="ftp://ftp.microsoft.com/developr/PlatformSDK/April2000/Msi/WinNT/x86/InstMsi.exe">ftp://ftp.microsoft.com/developr/PlatformSDK/April2000/Msi/WinNT/x86/InstMsi.exe</jump>.</p>
-
- <p>The installation is huge, but you don't need most of it. So you
- may do a <em>custom install</em> by just selecting "Build Environment" and
- choosing the required components. First select the top level Platform SDK.
- Then click the down arrow and make all of the components unavailable. Next open the
- "Build Environment" branch and select only the following items:</p>
- <ul>
- <li>Win32 API</li>
- <li>Component Services</li>
- <li>Web Services - Internet Explorer</li>
- </ul>
-
- <p><em>Important:</em> When the installation is complete you need to update VC6's
- include path to include <code>..\platformsdk\include\atl30</code>. You do this by
- choosing "Tools -> Options -> Directories". This path
- should be placed <ref>second</ref> after the normal PlatformSDK include.
- You change the order of the paths by clicking the up and down arrows.</p>
-
- <note>The order in which the directories appear on your path is important. Your
- first include path should be <code>..\platformsdk\include</code>. The second one
- should be <code>..\platformsdk\include\atl30</code>.</note>
- </s3>
-
- <s3 title="Building COM module for &XercesCName;">
- <p>Once you have set up your machine, build &XercesCName; COM module
- by choosing the project named 'xml4com' inside the workspace. Then select your
- build mode to be <em>xml4com - Win32 Release MinDependency</em>. Finally build the
- project. This will produce a DLL named <code>xerces-com.dll</code> which needs
- to be present in your path (on local machine) before you can use it.</p>
- </s3>
-
- <s3 title="Testing the COM module">
- <p>There are some sample test programs in the <code>test/COMTest</code>
- directory which show examples of navigating and searching an XML tree
- using DOM. You need to browse the HTML files in this directory using
- IE 5.0. Make sure that your build has worked properly, specially the
- registration of the ActiveX controls that happens in the final step.</p>
- <p>You may also want to check out the NIST DOM test suite at
- <jump href="http://xw2k.sdct.itl.nist.gov/BRADY/DOM/">http://xw2k.sdct.itl.nist.gov/BRADY/DOM/</jump>.
- You will have to modify the documents in the NIST suite to load the
- Xerces COM object instead of the MSIE COM object.</p>
- </s3>
- </s2>
-
-
<anchor name="UserDoc"/>
<s2 title="Building User Documentation">
<p>The user documentation (this very page that you are reading
@@ -225,40 +168,52 @@
the &XercesCName; module. These files reside in the
<code>doc</code> directory.</p>
- <p><em>Pre-requisites for building the user
- documentation are:</em></p>
+ <p><em>Pre-requisites for building the user documentation are:</em></p>
<ul>
<li>JDK 1.2.2 (or later).</li>
- <li>Xerces-J 1.0.1.<em>bundled</em></li>
- <li>Xalan-J 0.19.2.<em>bundled</em></li>
- <li>Stylebook 1.0-b2.<em>bundled</em></li>
- <li>The Apache Style files (dtd's and .xsl files).<em>bundled</em></li>
+ <li>Xerces-J 1.0.1 (provided by &XercesC3ToolsInstallDir;)</li>
+ <li>Xalan-J 0.19.2 (provided by &XercesC3ToolsInstallDir;)</li>
+ <li>Stylebook 1.0-b2 (provided by &XercesC3ToolsInstallDir;)</li>
</ul>
- <p>Invoke a command window and setup PATH to include the JDK 1.2.2 bin
- directory</p>
+ <p>Before proceeding, copy the contents of the &XercesC3ToolsInstallDir;
+ distribution into your <code>$XERCESCROOT</code>. Then invoke
+ a terminal or a command window and setup PATH to include the
+ JDK 1.2.2 bin directory. Next, cd to the <code>$XERCESCROOT</code>
+ source root directory, and enter:</p>
- <p>Next, cd to the &XercesCName; source drop root directory,
- and enter</p>
+<source>
+createDocs.bat (Windows)
+./createDocs.sh (UNIX)
+</source>
- <ul>
- <li>Under Windows:<br/>
- <code>createDocs</code></li>
- <li>Under Unix's:<br/>
- <code>sh createDocs.bat</code></li>
- </ul>
+ <p>This should generate the .html files in the 'doc/html' directory.</p>
+
+ <p>To regenerate the API documentation, you need to have at least
+ <jump href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</jump>
+ installed on your system.</p>
+
+ <p>If you want the API documentation to
+ contain dependency graphs, you also need to have <jump
+ href="http://www.research.att.com/sw/tools/graphviz/">GraphViz</jump> installed on
+ your system.</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 =
+ YES</code> into <code>HAVE_DOT = NO</code>.</p>
- <p>This should generate the .html files in the 'doc/html'
- directory.</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>
</s2>
<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 in a small number of folders, which should ease the porting
- effort. Please refer to <jump href="program-others.html#PortingGuidelines">Porting
+ isolated to a couple of files, which should ease the porting
+ effort. Please refer to <jump href="program-others-&XercesC3Series;.html#PortingGuidelines">Porting
Guidelines</jump> for further details.</p>
</s2>
@@ -315,11 +270,9 @@
<p>If you have read this page, followed the instructions, and
still cannot resolve your problem(s), there is more help. You
can find out if others have
- 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://issues.apache.org/jira/secure/BrowseProject.jspa?id=10510">Jira</jump>
- Apache bug database.</p>
+ solved this same problem before you, by checking the
+ <jump href="&MailURI;">&XercesCName; mailing list archives</jump> and
+ <jump href="&BugURI;">&XercesCName; bug database</jump>.</p>
</s2>
</s1>
Modified: xerces/c/trunk/doc/build-other.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/build-other.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/build-other.xml (original)
+++ xerces/c/trunk/doc/build-other.xml Mon Feb 25 07:35:02 2008
@@ -141,9 +141,9 @@
name based on the parser version (using apache xerces versioning)):</p>
<source>qsh:
cd <full path to &XercesCName;>/lib
-qar -cuv &XercesCUnixLib;&XercesCUnixSoName;.so *.o
+qar -cuv &XercesC3UnixLib;&XercesC3UnixSoName;.so *.o
will results in
-command = CRTBNDDIR BNDDIR(yourlib/libxercesc) TEXT('/yourlib/&XercesCName;/lib/&XercesCUnixLib;&XercesCUnixSoName;.so')
+command = CRTBNDDIR BNDDIR(yourlib/libxercesc) TEXT('/yourlib/&XercesCName;/lib/&XercesC3UnixLib;&XercesC3UnixSoName;.so')
command = ADDBNDDIRE BNDDIR(yourlib/libxercesc) OBJ((yourlib/LIBXERCESC *SRVPGM) )</source>
@@ -172,8 +172,8 @@
<source>
qsh:
cd <full path to &XercesCName;>/lib
-ln -s /qsys.lib/<outputdir>.lib/libxercesc.srvpgm &XercesCUnixLib;&XercesCUnixSoName;.so
-qar -cuv &XercesCUnixLib;&XercesCUnixSoName;.so *.o
+ln -s /qsys.lib/<outputdir>.lib/libxercesc.srvpgm &XercesC3UnixLib;&XercesC3UnixSoName;.so
+qar -cuv &XercesC3UnixLib;&XercesC3UnixSoName;.so *.o
</source>
<p>If you are on a v4 system using the ILE C++ PRPQ compiler (which is referred
@@ -183,9 +183,55 @@
<ul>
<li>src/xercesc/dom/impl/DOMDocumentImpl.cpp</li>
<li>src/xercesc/dom/impl/DOMDocumentImpl.hpp</li>
+ <li>src/xercesc/dom/deprecated/DocumentImpl.cpp</li>
+ <li>src/xercesc/dom/deprecated/DocumentImpl.hpp</li>
<li>src/xercesc/validators/common/ContentSpecNode.hpp</li>
</ul>
+ <p>Update the following routines in src/xercesc/dom/deprecated/DocumentImpl.cpp as follows:</p>
+<source>
+ void DocumentImpl::setUserData(NodeImpl* n, void* data)
+ {
+ if (!userData && data)
+ #ifdef __OS400__
+ userData = new RefHashTableOf<char>(29, false, new HashPtr());
+ #else
+ userData = new RefHashTableOf<void>(29, false, new HashPtr());
+ #endif
+ if (!data && userData)
+ userData->removeKey((void*)n);
+ else
+ #ifdef __OS400__
+ userData->put((void*)n,(char*)data);
+ #else
+ userData->put((void*)n,data);
+ #endif
+ }
+
+ void* DocumentImpl::getUserData(NodeImpl* n)
+ {
+ if (userData)
+ #ifdef __OS400__
+ return (void*)userData->get((void*)n);
+ #else
+ return userData->get((void*)n);
+ #endif
+ else
+ return null;
+ }
+</source>
+
+ <p>To update src/xercesc/dom/deprecated/DoumentImpl.hpp as follows:</p>
+
+<source>
+ #ifdef __OS400__
+ RefHashTableOf<char> *userData;
+ #else
+
+ RefHashTableOf<void> *userData;
+ #endif
+</source>
+
<p>Update the following routines in src/xercesc/dom/impl/DOMDocumentImpl.cpp as follows:</p>
<source>
void DOMDocumentImpl::setUserData(DOMNode* n, void* data)
@@ -382,13 +428,6 @@
<li>The DOMPrint project illustrates one such usage of the Xerces.framework.
</li>
</ul>
-
- <p>Projects for Apple's Project Builder environment, which is no longer supported
- under Mac OS X 10.3, are provided but may be out of date. You may need to add or
- delete files from the project in order to support changes in &XercesCName;. Please feel
- free to submit patches against these projects If you care about the Project Builder
- projects, and want to keep them up to date.
- </p>
</s3>
@@ -408,14 +447,14 @@
</li>
</ul>
-<source>setenv XERCESCROOT "<xerces-c-directory>"
+<source>export XERCESCROOT="<xerces-c-directory>"
cd src/xercesc
-./runConfigure -p macosx -n native
+./runConfigure -p macosx -n native -t native
make</source>
<ul>
<li>Similar instructions apply to build the samples and tests, though the
- <code>-n</code> flag is not used in these cases:
+ <code>-n</code> and <code>-t</code> flags are not used in these cases:
</li>
</ul>
Modified: xerces/c/trunk/doc/build-winunix.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/build-winunix.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/build-winunix.xml (original)
+++ xerces/c/trunk/doc/build-winunix.xml Mon Feb 25 07:35:02 2008
@@ -19,190 +19,97 @@
<!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="MinGW">Building on Windows using MinGW-MSYS</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.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++ 2005):</p>
-<source>&XercesCSrcInstallDir;\Projects\Win32\VC8\xerces-all\xerces-all.sln</source>
- <p>For MSVC Version 9.0 (Visual C++ 2008):</p>
-<source>&XercesCSrcInstallDir;\Projects\Win32\VC9\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.1) &XercesCSrcInstallDir;\Projects\Win32\VC7.1\xerces-all\XercesLib\XercesLib.vcproj
-(For MSVC V8) &XercesCSrcInstallDir;\Projects\Win32\VC8\xerces-all\XercesLib\XercesLib.vcproj
-(For MSVC V9) &XercesCSrcInstallDir;\Projects\Win32\VC9\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
+ &XercesC3SrcInstallDir; 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
+(For VC9) Projects\Win32\VC9\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
+(For VC9) Projects\Win32\VC9\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>
+ the &XercesC3WindowsLib;.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> 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.
+ <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.</note>
- 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 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>
- <li><code>make -f Xerces-all.mak</code>
- <br/>to build the dll and tests</li>
- </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.</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>
-
- <p>By default, autoconf on Cygwin and MinGW/MSYS doesn't build shared libraries,
- even if <code>configure</code> will detect it's possible; you will have to force
- it by specifying the <code>LDFLAGS=-no-undefined</code> option to <code>configure</code>
- </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">
- <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>
-
- <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>
-
- <p>Besides having all necessary build tools, you also need to know what
- compilers we have tested &XercesCName; on. The following table lists the
- relevant platforms and compilers.</p>
-
- &build-winunix-supported-platforms;
+ <s2 title="Building on UNIX/Linux/Mac OS X platforms">
- <!-- note about building on untested platforms - see entities.ent -->
- &build-winunix-note;
+ <p>&XercesCName; uses
+ <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>
+ Spending some time reading the following instructions will save
+ you a lot of wasted time and support-related e-mail communication.</p>
<p><em>Differences between the UNIX platforms:</em> The description below is
generic, but as every programmer is aware, there are minor differences
@@ -216,10 +123,6 @@
discussion assumes you are working on Linux, but it is with subtle
understanding that you know how to interpret it for the other UNIX flavors.</p>
- <note>If you wish to build &XercesCName; with ICU,
- look at the <jump href="build-misc.html#faq-1">Building &XercesCName; with ICU</jump>.
- It tells you where you can get ICU and how to build &XercesCName; with it.</note>
-
<s3 title="Setting build environment variables">
<p>Before doing the build, you must first set your environment variables
to pick-up the compiler.
@@ -227,7 +130,7 @@
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>
- </s3>
+ </s3>
<s3 title="Building &XercesCName; library">
<p>As mentioned earlier, to build &XercesCName; from the source distribution,
@@ -243,15 +146,15 @@
(called <code>configure</code>) is already in your <code>src/xercesc</code>
directory. If not, type:</p>
-<source>cd <full path to &XercesCSrcInstallDir;>
+<source>cd <full path to &XercesC3SrcInstallDir;>
./reconf</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.
+ 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>
- you need to make some decisions about what components you want to
+ <jump href="http://www.gnu.org/software/gcc/gcc.html">g++</jump>
+ 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
@@ -317,8 +220,8 @@
[..snip..]
checking for gcc... gcc
[..snip..]
-checking for libcurl...
-checking for libwww...
+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
@@ -396,48 +299,157 @@
</s3>
</s2>
-<!-- <anchor name="UNIX_SingleThread"/>
- <s2 title="Building &XercesCName; as a single-threaded library on Unix platforms">
- <p>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
+ "-p cygwin -c gcc -x g++" arguments.</p>
+
+ <p>Cygwin's GCC also has the ability to build MinGW targeted binaries.
+ This is supported via the -mno-cygwin compiler switch. In that case the
+ arguments to runConfigure should be
+ '-p mingw-msys -c gcc -x g++ -z -mno-cygwin -l -mno-cygwin -C --host=i686-mingw32'.
+ Note that both the compiler and linker flags need to be set.</p>
+
+ <p>Also 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>By default, autoconf on Cygwin and MinGW/MSYS doesn't build shared libraries,
+ even if <code>configure</code> will detect it's possible; you will have to force
+ it by specifying the <code>LDFLAGS=-no-undefined</code> option to <code>configure</code>
+ </p>
+
+ <p>There is an issue with the gcc/g++ compiler version 2.95, where C++
+ exceptions thrown from a DLL will cause the application to crash, regardless
+ of whether there is a "catch" statement. This bug doesn't occur in tests
+ using gcc 3.1 or 3.2, so it is recommended that you use gcc 3.1 or higher.</p>
+ </s2>
+ <anchor name="MinGW"/>
+ <s2 title="Building on Windows using MinGW">
+ <p><em>Do not jump into the build directly before reading this.</em></p>
- <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>
--->
+ <p>&XercesCName; may be built in the
+ <jump href="http://www.mingw.org/msys.shtml">MinGW-MSYS</jump> environment for use
+ by MinGW applications. As with the <jump href="#UNIX">UNIX</jump>
+ platforms, &XercesCName; on MinGW uses
+ <jump href="http://www.gnu.org">GNU</jump> tools. Therefore, with a
+ couple of notable exceptions, &XercesCName; on MinGW is built using
+ the same instructions as the UNIX platforms. The build environment
+ variable XERCESCROOT must be set to the proper path containing the
+ &XercesCName; sources and <em>runConfigure</em> must be run with the
+ "-pmingw-msys -cgcc -xg++" arguments. It is also possible to build
+ &XercesCName; libraries for MinGW using Cygwin. For more information
+ on how to do this see the <jump href="#CygWin">Building on Windows
+ using Cygwin</jump> section.</p>
+
+ <p>Note that MinGW is different from the UNIX platforms in the way
+ that it finds libraries at run time. While UNIX platforms may use the
+ environment variable LD_LIBRARY_PATH, MinGW uses the PATH environment
+ variable.</p>
+
+ <p>When linking against the static version of &XercesCName;, be sure to
+ use the '-DXML_LIBRARY' compiler flag. Otherwise the functions in the
+ header files will be marked as to be imported from a DLL and the linker will fail.</p>
+
+ <p>Also note that you can run into a bug found in older MinGW's dllwrap utility,
+ which is used by &XercesCName; build system to link DLLs. For more information
+ see the following <jump href="http://marc.info/?l=xerces-c-users&m=118891009725180&w=2">
+ mailing list post</jump>.</p>
+
+ <p>There is an issue with the gcc/g++ compiler version 2.95, where C++
+ exceptions thrown from a DLL will cause the application to crash, regardless
+ of whether there is a "catch" statement. This bug doesn't occur in tests
+ using gcc 3.1 or 3.2, so it is recommended that you use gcc 3.1 or higher.</p>
+ </s2>
+
+ <anchor name="WinBorlandBuilder"/>
+ <s2 title="Building on Windows using Borland C++ Builder">
+ <p>&XercesCName; source distribution comes with Borland C++ Builder 6 projects to help you
+ 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> &XercesC3SrcInstallDir;\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> &XercesC3SrcInstallDir;\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> &XercesC3SrcInstallDir;\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 &XercesC3SrcInstallDir;\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 &XercesC3SrcInstallDir;\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 &XercesC3WindowsLib;.lib library and also make sure that
+ the associated DLL is somewhere in your path.</p>
+ </s3>
+ </s2>
</s1>
Modified: xerces/c/trunk/doc/build.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/build.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/build.xml (original)
+++ xerces/c/trunk/doc/build.xml Mon Feb 25 07:35:02 2008
@@ -21,39 +21,39 @@
<s1 title="Build Instructions">
<s2 title="Building on Windows and UNIX">
- <p>Read the <jump href="build-winunix.html">Building on Windows and UNIX</jump> document
+ <p>Read the <jump href="build-winunix-&XercesC3Series;.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-&XercesC3Series;.html#WinNT">Building on Windows using Microsoft Visual C++</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#UNIX">Building on UNIX/Linux/Mac OS X platforms</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#CygWin">Building on Windows using Cygwin</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#MinGW">Building on Windows using MinGW-MSYS</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#WinBorlandCC">Building on Windows using Borland C++</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#WinBorlandBuilder">Building on Windows using Borland C++ Builder</jump></li>
+ <li><jump href="build-winunix-&XercesC3Series;.html#WinIntel">Building 64 bit libraries on Windows using Intel C++</jump></li>
</ul>
</s2>
<s2 title="Building on Other Platforms">
- <p>Read the <jump href="build-other.html">Building on Other Platforms</jump> document
+ <p>Read the <jump href="build-other-&XercesC3Series;.html">Building on Other Platforms</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-other.html#iSeries">Building &XercesCName; on iSeries (AS/400)</jump></li>
- <li><jump href="build-other.html#Mac">Building &XercesCName; on Macintosh</jump></li>
+ <li><jump href="build-other-&XercesC3Series;.html#iSeries">Building &XercesCName; on iSeries (AS/400)</jump></li>
+ <li><jump href="build-other-&XercesC3Series;.html#Mac">Building &XercesCName; on Macintosh</jump></li>
</ul>
</s2>
<s2 title="Other Build Instructions">
- <p>Read the <jump href="build-misc.html">Other Build Instructions</jump> document
+ <p>Read the <jump href="build-misc-&XercesC3Series;.html">Other Build Instructions</jump> document
or jump directly to:</p>
<ul>
- <li><jump href="build-misc.html#ICUPerl">Building &XercesCName; with ICU</jump></li>
- <li><jump href="build-misc.html#RPMLinux">Building &XercesCName; using RPM on Linux</jump></li>
- <li><jump href="build-misc.html#WinCOM">Building &XercesCName; COM Wrapper on Windows</jump></li>
- <li><jump href="build-misc.html#UserDoc">Building User Documentation</jump></li>
- <li><jump href="build-misc.html#PortInfo">I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?</jump></li>
- <li><jump href="build-misc.html#XMLChInfo">What should I define XMLCh to be?</jump></li>
- <li><jump href="build-misc.html#HelpInfo">Where can I look for more help?</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#ICUPerl">Building &XercesCName; with ICU</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#RPMLinux">Building &XercesCName; using RPM on Linux</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#WinCOM">Building &XercesCName; COM Wrapper on Windows</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#UserDoc">Building User Documentation</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#PortInfo">I wish to port &XercesCProjectName; to my favourite platform. Do you have any suggestions?</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#XMLChInfo">What should I define XMLCh to be?</jump></li>
+ <li><jump href="build-misc-&XercesC3Series;.html#HelpInfo">Where can I look for more help?</jump></li>
</ul>
</s2>
Modified: xerces/c/trunk/doc/dom3.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/dom3.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/dom3.xml (original)
+++ xerces/c/trunk/doc/dom3.xml Mon Feb 25 07:35:02 2008
@@ -21,7 +21,7 @@
<s1 title="DOM Level 3 Support">
<s2 title="Introduction">
<p>
- The &XercesCName; &XercesCVersion; contains an implementation of the W3C DOM Level 3 as specified in </p>
+ The &XercesCName; &XercesC3Version; contains an implementation of the W3C DOM Level 3 as specified in </p>
<ul>
<li><jump href="http://www.w3.org/TR/DOM-Level-3-Core/">
DOM Level 3.0 Core Specification</jump>, Version 1.0 W3C Recommendation 07 April 2004 and</li>
@@ -32,7 +32,7 @@
</s2>
<s2 title='Implementation of DOM Level 3 Core'>
- <p>The following are NOT implemented in &XercesCName; &XercesCVersion;.</p>
+ <p>The following are NOT implemented in &XercesCName; &XercesC3Version;.</p>
<ul>
<li>
<code>DOMError</code>: setRelatedException
@@ -47,7 +47,7 @@
</s2>
<s2 title='Implementation of DOM Level 3 Load and Save'>
- <p>The following are implemented in &XercesCName; &XercesCVersion;.</p>
+ <p>The following are implemented in &XercesCName; &XercesC3Version;.</p>
<ul>
<li>
<code>DOMLSParser</code>: parseWithContext().
Modified: xerces/c/trunk/doc/domcount.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/domcount.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/domcount.xml (original)
+++ xerces/c/trunk/doc/domcount.xml Mon Feb 25 07:35:02 2008
@@ -55,7 +55,7 @@
<em>-v=never</em> will not use any validation<br/>
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
<p>Here is a sample output from DOMCount</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC3InstallDir;-linux/samples/data
DOMCount -v=always personal.xml
personal.xml: 20 ms (37 elems)</source>
Modified: xerces/c/trunk/doc/domprint.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/domprint.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/domprint.xml (original)
+++ xerces/c/trunk/doc/domprint.xml Mon Feb 25 07:35:02 2008
@@ -67,7 +67,7 @@
<em>-v=never</em> will not use any validation<br/>
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
<p>Here is a sample output from DOMPrint</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC3InstallDir;-linux/samples/data
DOMPrint -v=always personal.xml
<?xml version="1.0" encoding="iso-8859-1"?>
Modified: xerces/c/trunk/doc/enumval.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/enumval.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/enumval.xml (original)
+++ xerces/c/trunk/doc/enumval.xml Mon Feb 25 07:35:02 2008
@@ -36,7 +36,7 @@
data structures.
</source>
<p>Here is a sample output from EnumVal</p>
-<source>cd &XercesCInstallDir;-linux/samples/data
+<source>cd &XercesC3InstallDir;-linux/samples/data
EnumVal personal.xml
ELEMENTS:
Modified: xerces/c/trunk/doc/faq-build.xml
URL: http://svn.apache.org/viewvc/xerces/c/trunk/doc/faq-build.xml?rev=630879&r1=630878&r2=630879&view=diff
==============================================================================
--- xerces/c/trunk/doc/faq-build.xml (original)
+++ xerces/c/trunk/doc/faq-build.xml Mon Feb 25 07:35:02 2008
@@ -26,17 +26,17 @@
<a>
- <p>&XercesCName; &XercesCVersion; now supports C++ Namespace.</p>
-
+ <p>&XercesCName; &XercesC3Version; now supports C++ Namespace.</p>
+
<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.
</p>
-
- <p>See the Programming Guide <jump href="program-others.html#CPPNamespace">
+
+ <p>See the Programming Guide <jump href="program-others-&XercesC3Series;.html#CPPNamespace">
Using C++ Namespace</jump> for details.
</p>
@@ -53,10 +53,10 @@
<p>Your application somehow has picked up the Microsoft SDK header <code>Msxml.h</code>
which has its own typedef of <code>DOMDocument</code>. This confuses
- with the &XercesCName; &XercesCVersion; <code>&XercesCNamespace;::DOMDocument</code>
+ with the &XercesCName; &XercesC3Version; <code>&XercesC3Namespace;::DOMDocument</code>
and thus lead to the compilation errors.</p>
- <p> Qualifying the use of DOMDocument in your application explicitly e.g.
+ <p> Qualifier 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>
@@ -96,10 +96,10 @@
<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>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
+ the same version as the ones used to build the binary. Different OS and
compiler versions might cause unresolved linking problems or compilation
errors. If the versions are different, rebuild the &XercesCName; library on
your system before building your application. If you're using ICU (which is
@@ -108,13 +108,13 @@
<li>Check that the library path is set properly and that the correct
versions of <code>gmake</code> and <code>autoconf</code> are on your system.</li>
<li>If C++ Namespace support is ENABLED (all the binary distributions of &XercesCName;
- &XercesCVersion; are built with C++ Namespace enabled), users' applications
- must namespace qualify all the &XercesCName; classes, data and variables.
- See the Programming Guide <jump href="program-others.html#CPPNamespace">
+ &XercesC3Version; are built with C++ Namespace enabled), users' applications
+ must namespace qualify all the &XercesCName; classes, data and variables.
+ See the Programming Guide <jump href="program-others-&XercesC3Series;.html#CPPNamespace">
Using C++ Namespace</jump> for details.</li>
- <li>If you are using Microsoft Visual Studio .NET 2003 or 2005, check that the
- option "Treat wchar_t as a built-in type" has been set to the same value
- used to build Xerces</li>
+ <li>If you are using Microsoft Visual Studio .NET 2003, 2005, or 2008, check that the
+ option "Treat wchar_t as a built-in type" has been set to the same value
+ used to build Xerces.</li>
</ol>
</a>
</faq>
@@ -162,14 +162,14 @@
from Apache, you must have the &XercesCName; runtime library available from
your path settings.
</p>
- <p>On Windows this library is called <code>&XercesCWindowsDLL;.dll</code>
+ <p>On Windows this library is called <code>&XercesC3WindowsDLL;.dll</code>
which must be available from your <code>PATH</code> settings. (Note that there are
separate debug and release dlls for Windows. The release dll is named
- <code>&XercesCWindowsDLL;.dll</code>, and the debug dll
- is named <code>&XercesCWindowsDLL;d.dll)</code>.
+ <code>&XercesC3WindowsDLL;.dll</code>, and the debug dll
+ is named <code>&XercesC3WindowsDLL;d.dll)</code>.
</p>
- <p>On UNIX platforms the library is called &XercesCUnixLib;.so.&XercesCUnixSoName; (or
- &XercesCUnixLib;&XercesCUnixSoName;.so or &XercesCUnixLib;.sl.&XercesCUnixSoName;)
+ <p>On UNIX platforms the library is called &XercesC3UnixLib;.so.&XercesC3UnixSoName; (or
+ &XercesC3UnixLib;&XercesC3UnixSoName;.so or &XercesC3UnixLib;.sl.&XercesC3UnixSoName;)
which must be available from your <code>LD_LIBRARY_PATH</code>
(or <code>LIBPATH</code> or <code>SHLIB_PATH</code>) environment variable.</p>
@@ -183,6 +183,11 @@
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, &XercesC3SrcInstallDir;/msg, where the message files reside.
+ </p>
+
</a>
</faq>
@@ -257,9 +262,9 @@
<source>
try {
- XERCES_CPP_NAMESPACE_QUALIFIER XMLPlatformUtils::Initialize();
+ XMLPlatformUtils::Initialize();
}
-catch (const XERCES_CPP_NAMESPACE_QUALIFIER XMLException& toCatch) {
+catch (const XMLException& toCatch) {
// Do your failure processing here
}</source>
@@ -309,8 +314,8 @@
<faq title="First-chance exception in Microsoft debugger">
- <q>"First-chance exception in DOMPrint.exe (KERNEL32.DLL): 0xE06D7363:
- Microsoft C++ Exception." I am always getting this message when I am using the
+ <q>First-chance exception in DOMPrint.exe (KERNEL32.DLL): 0xE06D7363:
+ Microsoft C++ Exception. I am always getting this message when I am using the
parser. My programs are terminating abnormally. Even the samples are giving
this exception. I am using Visual C++ 6.0 with latest service pack
installed.</q>
@@ -327,7 +332,7 @@
<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
@@ -338,59 +343,62 @@
</faq>
<faq title="Cannot load message domain, Xerces Panic Error">
- <q>"Cannot load message domain, Xerces Panic Error"?</q>
+ <q>Cannot load message domain, Xerces Panic Error?</q>
<a>
- <p>If the parser is built with icu message loader (like IBM XML4C binaries),
- 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.
+ <p>If the parser is built with icu message loader (like IBM XML4C binaries),
+ you need to make sure that the message library (for the exact name see
+ <jump href="faq-distrib-&XercesC3Series;.html#faq-2">FAQ: Which DLLs do I need to distribute
+ with my application?</jump>) 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 &XercesC3SrcInstallDir;/msg.
</p>
- <p>If the parser is built with iconv message catalog loader, you need to make sure that the message
+ <p>If the parser is built with iconv message 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.
- </p>
+ or is located in the directory pointed to by the environment variable XERCESC_NLS_HOME, or
+ at &XercesC3SrcInstallDir;/msg.
+ </p>
</a>
</faq>
<faq title="Why my document is valid on some platforms while invalid on others">
- <q>"Why my document is valid on some platform while invalid on others"?</q>
+ <q>Why my document is valid on some platform while invalid on others?</q>
<a>
- <p>The parser relies on the system call, strtod(), to parse a string representation
+ <p>The parser relies on the system call, strtod(), to parse a string representation
of a double/float data. In the case of no invalid characters found, the strtod()
- returns a double/float value if it is representable on that platform, or raises
- ERANGE to indicate either underflow or underflow occurs. And the parser assigns
- zero to the said data if underflow is found.
+ returns a double/float value if it is representable on that platform, or raises
+ ERANGE to indicate either underflow or underflow occurs. And the parser assigns
+ zero to the said data if underflow is found.
</p>
- <p>The threshold, where the strtod() decides if an underflow occurs, varies on
- platforms. On windows, it is roughly the order of e-308, on Linux, e-325, and
+ <p>The threshold, where the strtod() decides if an underflow occurs, varies on
+ platforms. On windows, it is roughly the order of e-308, on Linux, e-325, and
on AIX, HP and Solaris, e-324.
- </p>
- <p>So in an instance document, a data of value 1.0e-310 from a type with minExclusive 0,
+ </p>
+ <p>So in an instance document, a data of value 1.0e-310 from a type with minExclusive 0,
is considered invalid on windows (since it is converted to 0 and therefore violates
- the minExclusive constraint), but valid on other unix platforms (since it remains
- the original value).
+ the minExclusive constraint), but valid on other unix platforms (since it remains
+ the original value).
</p>
<p>The discussion above applies to data in xsd file as well.
- </p>
+ </p>
</a>
</faq>
-
- <faq title='Regenerating (API) documentation?'>
- <q>How do I regenerate the (API) documentation?</q>
+
+ <faq title="How do I regenerate the documentation?">
+ <q>How do I regenerate the documentation?</q>
<a>
<p>To use the internal XML based application that creates the
documentation, you must have a Java Virtual machine installed
on your system. The application itself, written in Java, is
- part of Xerces.</p>
+ provided in the &XercesC3ToolsInstallDir; distribution. You
+ should copy its contents into your <code>&XercesC3SrcInstallDir;</code>
+ directory.</p>
- <p>To regenerate the documentation, go to Xerces directory
+ <p>To regenerate the documentation, go to &XercesC3SrcInstallDir;
and start <code>createDocs.sh</code> (for Unix) or
<code>createdocs.bat</code> (for Windows). The result can be
- found in the subdirectory <code>doc/html</code>.</p>
+ found in directory <code>&XercesC3SrcInstallDir;/doc/html</code>.</p>
<p>
To regenerate the API documentation, you need to have at least
@@ -400,19 +408,15 @@
<p>If you want the API documentation to
contain dependency graphs, you also need to have <jump
href="http://www.research.att.com/sw/tools/graphviz/">GraphViz</jump> installed on
- your system. (Note that some people object to the
- <jump
- href="http://www.research.att.com/sw/tools/graphviz/license/index.html">GraphViz
- license</jump>, so there are Linux distributions that do not
- include it.)</p>
+ your system.</p>
<p>If you do not have GraphViz, or do not want to use it, you
- have to edit file <code>doc/Doxyfile</code> and change <code>HAVE_DOT =
- YES</code> into <code>HAVE_DOT = NO</code>.</p>
+ have to edit file <code>&XercesC3SrcInstallDir;/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>doc/</code> and start Doxygen. The result can be
- found in directory <code>doc/html/apiDocs</code>.</p>
+ <code>&XercesC3SrcInstallDir;/doc/</code> and start Doxygen. The result can be
+ found in directory <code>&XercesC3SrcInstallDir;/doc/html/apiDocs</code>.</p>
</a>
</faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org