You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by sh...@apache.org on 2012/06/16 06:28:16 UTC
svn commit: r1350859 [2/7] - in /xalan/c/trunk/xdocs: ./ html/ html/apiDocs/
sources/ sources/xalan-graphic/ sources/xalan/ sources/xslt-resources/
style/ style/dtd/
Added: xalan/c/trunk/xdocs/sources/xalan/License
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/License?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/License (added)
+++ xalan/c/trunk/xdocs/sources/xalan/License Sat Jun 16 04:28:14 2012
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
\ No newline at end of file
Added: xalan/c/trunk/xdocs/sources/xalan/NOTICE
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/NOTICE?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/NOTICE (added)
+++ xalan/c/trunk/xdocs/sources/xalan/NOTICE Sat Jun 16 04:28:14 2012
@@ -0,0 +1,17 @@
+ =======================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License. ==
+ == Version 2.0, in this case for the Apache Xalan distribution. ==
+ =======================================================================
+
+ Apache XALAN-C
+ Copyright (c) 1999-2012 The Apache Software Foundation
+
+ This product includes software developed at
+ The Apache Software Foundation (http://www.apache.org/).
+
+ This software is based on the ASF XERCES-C project.
+
+ Portions of this software were originally based on the following:
+ - software copyright (c) 1999, IBM Corporation. (http://www.ibm.com).
+
+ Additional copyright submissions and contributions:
Added: xalan/c/trunk/xdocs/sources/xalan/Notice-Issue.txt
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/Notice-Issue.txt?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/Notice-Issue.txt (added)
+++ xalan/c/trunk/xdocs/sources/xalan/Notice-Issue.txt Sat Jun 16 04:28:14 2012
@@ -0,0 +1,33 @@
+The CurrentSVN sources conform to the ASF License version 2.0.
+
+The ASF licensing information needs to be updated in the documentation.
+
+A copy of The Apache Software Foundation License version 2.0 needs to
+replace the following file in the repository.
+
+ xalan/c/trunk/xdocs/sources/xalan/License
+
+A NOTICE file needs to be ratified by the XALAN PMC and added to the
+repository documentation.
+
+ xalan/c/trunk/xdocs/sources/xalan/NOTICE
+
+Here is some possible text for the NOTICE file.
+
+ =======================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License. ==
+ == Version 2.0, in this case for the Apache Xalan distribution. ==
+ =======================================================================
+
+ Apache XALAN-C
+ Copyright (c) 1999-2011 The Apache Software Foundation
+
+ This product includes software developed at
+ The Apache Software Foundation (http://www.apache.org/).
+
+ This software is based on the ASF XERCES-C project.
+
+ Portions of this software were originally based on the following:
+ - software copyright (c) 1999, IBM Corporation. (http://www.ibm.com).
+
+ Additional copyright submissions and contributions:
Added: xalan/c/trunk/xdocs/sources/xalan/STATUS
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/STATUS?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/STATUS (added)
+++ xalan/c/trunk/xdocs/sources/xalan/STATUS Sat Jun 16 04:28:14 2012
@@ -0,0 +1,20 @@
+<s3 title="Version of &xml4c; to use">
+<p>&xslt4c-current; has been tested with &xml4c-used;.</p>
+<p>For information about including the Xerces-C++ libraries on the path, see <link idref="install" anchor="path">Setting up the system path</link>.</p>
+<p><em>Important:</em> You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.</p>
+<p>If you compile both &xslt4c; and &xml4c; from distribution sources using the same platform and compiler, you will avoid most of the compatibility issues.</p>
+
+</s3><anchor name="to-do"/>
+<s3 title="To-do tasks for future &xslt4c; releases">
+ <ul>
+ <li>Update the documentation</li>
+ <li>Performance improvements</li>
+ <li>Add a more complete set of EXSLT functions</li>
+ <li>Add support for extension elements</li>
+ <li>Fix any conformance bugs we or our users find</li>
+ <li>Fix compiler and platform support issues</li>
+ <li>Add XPath2 support into &xslt4c;</li>
+ </ul>
+ <p>Watch the <human-resource-ref idref="xalandev"/> for more information and for ideas about how you can get involved.
+</p>
+</s3>
Added: xalan/c/trunk/xdocs/sources/xalan/build_instruct.xml
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/build_instruct.xml?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/build_instruct.xml (added)
+++ xalan/c/trunk/xdocs/sources/xalan/build_instruct.xml Sat Jun 16 04:28:14 2012
@@ -0,0 +1,310 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<s1 title="Building &xslt4c;">
+<anchor name="build"/>
+<p>This section is obsolete and is being rewritten.
+See: <jump href="BUILD-LIBS.html">BUILD-LIBS.html</jump></p>
+<p>This page was created for users who have downloaded the source distribution of &xslt4c; and are looking for guidance on how to
+ build the &xslt4c; libraries themselves.</p>
+<ul>
+ <li><link anchor="rebuild">Rebuilding &xslt4c;</link></li>
+ <li><link idref="samples" anchor="rebuilding">Rebuilding sample applications</link></li>
+</ul>
+
+<anchor name="rebuild"/>
+<s3 title="Rebuilding &xslt4c;">
+<ul>
+ <li><link anchor="needed">What you need from the distributions</link></li>
+ <li><link anchor="win32">Steps for doing a Windows Build</link></li>
+ <li><link anchor="dotNet">Steps for doing a Windows Build with Visual Studio .NET</link></li>
+ <li><link anchor="unix">Steps for doing a UNIX build</link></li>
+ <li><link anchor="locale">Steps for doing a Build with Message Localization Support</link></li>
+ <!--
+ <li><link anchor="xercesdepdom">Steps for doing a Build with Xerces Deprecated DOM Support</link></li>
+ -->
+</ul>
+</s3>
+
+<anchor name="needed"/>
+<s3 title="What you need from the distributions">
+<p>To rebuild &xslt4c;, you need the &xslt4c; source files, the &xml4c; header files, and for Windows the &xml4c; .lib file.
+ If you want to rebuild with the ICU, you will need to download the ICU source package to build the ICU libraries. </p>
+<note>You can also download &xslt4c; source distributions from <resource-ref idref="xslt4c-distdir"/>: &xslt4c-dist;-src.zip
+ and &xslt4c-dist;-src.tar.gz. &xml4c; source distributions are available from <resource-ref idref="xml4c-distdir"/>:
+ &xml4c-dist;-src.zip and &xml4c-dist;-src.tar.gz.</note>
+<p>Keep in mind that at any given point in time the &xslt4c; and &xml4c; source trees in the Apache XML repository may not
+ be consistent. When we release a version of &xslt4c; we certify that it is compatible with a given version of &xml4c;. To
+ be safe, use the Xerces distributions that we certify as compatible. Reminder: &xslt4c-current; is compatible with
+ &xml4c-used;.</p>
+<p>For information on using the <resource-ref idref="icu"/>, see <link idref="usagepatterns" anchor="icu">Using the ICU</link>.
+ The recommended version of ICU for &xslt4c-current; is &icu-current;. You may be able to use newer ICU releases as they appear.</p>
+</s3>
+
+<anchor name="win32"/>
+<s3 title="Steps for doing a Windows build">
+<p>To build &xslt4c; on Windows, you need &xml4c; and a C++ compiler for Windows (either MS Visual C++ 6.0 installed with Service
+ Pack 5 for Visual C++ OR Visual Studio .NET).</p>
+<p>If you are using a different Service Pack, you must rebuild all of the Xerces and Xalan binaries.</p>
+<p>Before you do the following, be sure you have <link idref="install" anchor="windowspath">provided Visual C++ the paths to
+ the Xerces headers and libraries</link>.</p>
+<ol>
+ <li>Create the XERCESCROOT environment variable and set it to the path of the root directory of &xml4c;.</li>
+ <li>If you are building with ICU, create the ICUROOT environment variable and set it the the path of the ICU root directory.</li>
+ <li>Use Visual C++ to open the Xalan workspace (.dsw) from the &xslt4c-win_root;\Projects\Win32\VC6. If you are building with
+ ICU, then use XalanICU.dsw. Otherwise, open the Xalan.dsw workspace.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT and XERCESCROOT to take effect.</note>
+ <br/>
+ As an alternative method to the steps described above, would be to go to "Tools" and select "Options" from Visual C++. From the
+ "Options" window, click on the "Directories" tab and do the following:
+ <ol>
+ <li>Show Directories for: Executable files. Add the Xerces bin directory to the list.</li>
+ <li>Show Directories for: Include files. Add the Xerces include directory to the list. If you are building with ICU, add the
+ ICU include directory to the list as well.</li>
+ <li>Show Directories for: Library files. Add the Xerces lib directory to the list. If you are building with ICU, add the ICU
+ lib directory to the list as well.</li>
+ </ol></li>
+</ol>
+<!-- -->
+<note>To recompile existing applications without changing your source code, be sure to modify your Project settings to pick up the
+ Xalan headers in its new location. (see image below)</note>
+<p><img src="options-sane.gif" alt="Visual C++ 6.0 Include Directories change"/></p>
+<!-- -->
+</s3>
+
+<anchor name="dotNet"/>
+<s3 title="Steps for doing a Windows Build with Microsoft Visual Studio .NET">
+<p>For users who want to build with Visual Studio .NET,</p>
+<ol>
+ <li>Create the XERCESCROOT environment variable and set it to the path of the root directory of &xml4c;.</li>
+ <li>If you are building with ICU, create the ICUROOT environment variable and set it to the path of the ICU root directory.</li>
+ <li>Use Visual Studio .NET to open the Xalan solution (.sln) from the &xslt4c-win_root;\Projects\Win32\VC7.1. If you are building
+ with ICU, then use XalanICU.sln. Otherwise, open the Xalan.sln solution file.<br/><br/>
+ <note>You may need to restart Visual Studio .NET in order for ICUROOT and XERCESCROOT to take effect.</note>
+ <br/>
+ An alternative method to the steps described above, would be to go to "Tools" and select "Options" from Visual Studio .NET. From
+ the "Options" window, click on the "Projects" folder to expand the list. Select "VC++ Directories" from the list and do the following:
+ <ol>
+ <li>Show Directories for: Executable files. Add the Xerces bin directory to the list.</li>
+ <li>Show Directories for: Include files. Add the Xerces include directory to the list. If you are building with ICU, add the
+ ICU include directory to the list as well.</li>
+ <li>Show Directories for: Library files. Add the Xerces lib directory to the list. If you are building with ICU, add the ICU
+ lib directory to the list as well.</li>
+ </ol></li>
+</ol>
+<!-- -->
+<note>To recompile existing applications without changing your source code, be sure to modify your Project settings to pick up the
+ Xalan headers in its new location. (see image below)</note>
+<p><img src="NET_options.jpg" alt="Visual Studio .NET Include Directories change"/></p>
+<!-- -->
+</s3>
+
+<anchor name="unix"/>
+<s3 title="Steps for doing a UNIX build">
+<p>For users who want to build in the UNIX environment,</p>
+<ol>
+ <li>The Xalan build files are written for GNU make, and will not work with other make utilities.<br/><br/></li>
+ <li>Set the XERCESCROOT environment variable to the path to the root directory of &xml4c;.<br/><br/></li>
+ <li>Set the XALANCROOT environment variable to the path to the c directory in the root directory of the &xslt4c;
+ distribution. For example, if the distribution is located in "/home/mydir", you would set the XALANCROOT to
+ "/home/mydir/&xslt4c-unix_root;". <br/><br/></li>
+ <li>(Optional) If you decide to build with ICU, integrate the build with ICU by installing the ICU (see <link
+ idref="usagepatterns" anchor="icu">Using the ICU</link>) and defining XALAN_USE_ICU to a value, for example:
+ export XALAN_USE_ICU=true. Set the ICUROOT environment variable to the path to the root directory of ICU.
+ Note that building Xalan with ICU requires that Xerces must also be built with ICU.<br/><br/></li>
+ <li>Change directory to XALANCROOT. You can also build Xalan-C outside of the source tree, but you will need to adjust the path to the
+ runConfigure script in the next step.<br/><br/></li>
+ <li>Run the runConfigure utility and provide the platform, C compiler, and C++ compiler flags as
+ indicated below. The runConfigure utility is used to generate the appropriate Makefile for
+ the desired build platform based on the options specified by the user. Valid options for the
+ runConfigure utility are:<br/><br/>
+ <code>./runConfigure -p <value> -c <value> -x <value> [-[flag] <value>]</code><br/><br/>
+ <table>
+ <tr><th>flag</th><th>Description</th></tr>
+ <tr><td>p</td><td>Build platform. Option must be provided by user. Valid values <br/>include:
+ aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp-11-ia64, irix,<br/>
+ tru64, macosx, cygwin. </td></tr>
+ <tr><td>c</td><td>C compiler name. Example: gcc, cc, c89, xlc_r, etc.</td></tr>
+ <tr><td>x</td><td>C++ compiler name. Example: g++, xlC_r, CC, etc.</td></tr>
+ <tr><td>d</td><td>Indicates build is a debug build. Takes no values. Default is no <br/>debug.</td></tr>
+ <tr><td>t</td><td>Transcoder to use. Valid value is 'icu'. Default is null.</td></tr>
+ <tr><td>m</td><td>Type of localization support method. Valid values include: inmem, <br/>icu, and nls.
+ Default is inmem.</td></tr>
+ <tr><td>M</td><td>Locale for Message Localization Support. Default is "en_US"</td></tr>
+ <tr><td>r</td><td>Threads option. Valid values include: pthread or dce. Default is <br/>pthread.
+ (valid on HP-UX only)</td></tr>
+ <tr><td>b</td><td>Specify whether it is a 32-bit or 64-bit build. Valid values are 32 <br/>and 64.
+ Default is 32-bit</td></tr>
+ <tr><td>P</td><td>Install root directory. Used if invoking build with gmake install or <br/>gmake
+ install-package. Default install root directory is /usr/local</td></tr>
+ <tr><td>l</td><td>Extra link options other than the default. Default is null</td></tr>
+ <tr><td>z</td><td>Extra compiler options other than the default. Default is null</td></tr>
+ <tr><td>C</td><td>Extra configuration options.</td></tr>
+ <tr><td>h</td><td>To get help on the above commands. Default is no help.</td></tr>
+ </table><br/>
+ <ref>Linux using GCC:</ref> <code>./runConfigure -p linux -c gcc -x g++</code><br/>
+ <ref>Linux using the Intel compiler:</ref> <code>./runConfigure -p linux -c icc -x icc</code><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r</code><br/><br/>
+ <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -b 64</code><br/><br/>
+ <ref>Cygwin (32-bit):</ref> <code>./runConfigure -p cygwin -c gcc -x g++</code><br/><br/>
+ <ref>HP-UX 11 (32-bit):</ref> <code>./runConfigure -p hp-11 -c cc -x aCC</code><br/><br/>
+ <ref>HP-UX 11 (64-bit):</ref> <code>./runConfigure -p hp-11 -c cc -x aCC -b 64</code><br/><br/>
+ <ref>HP-UX 11 for Itanium (32-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x aCC</code><br/><br/>
+ <ref>HP-UX 11 for Itanium (64-bit):</ref> <code>./runConfigure -p hp-11-ia64 -c cc -x aCC -b 64</code><br/><br/>
+ <ref>Solaris (32-bit):</ref> <code>./runConfigure -p solaris -c cc -x CC</code><br/><br/>
+ <ref>Solaris (64-bit):</ref> <code>./runConfigure -p solaris -c cc -x CC -b 64</code><br/><br/>
+ if you choose to install the distribution after building the libraries and executables,
+ then you will need to indicate where you would like the distribution to be installed.
+ To specify the install directory for your distribution, specify the flag -P <install directory>.
+ for example, building and installing on the AIX platform:<br/><br/>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -P $HOME/my_xalan</code><br/><br/>
+ <note>The standard binary directories bin, lib, and include are created in the specified directory only if the install or
+ install-package option is specified in the build process.<br/><br/></note>
+ To see the other runConfigure flags you may include, use the help flag:<br/><br/>
+ <code>./runConfigure -h</code><br/><br/></li>
+ <li>Purge the previous build:<br/><br/>
+ <code> make clean</code><br/><br/></li>
+ <li>Run the new build:<br/><br/>
+ <code>make</code><br/>
+ or<br/>
+ <code>make <ref>targ</ref></code><br/><br/>
+ where <ref>targ</ref> can be one of:
+ <table>
+ <tr><th>targ</th><th>Description</th></tr>
+ <tr><td>all</td><td>Build the libraries and Xalan executable. This is the default target <br/>if no targ
+ is specified.</td></tr>
+ <tr><td>clean</td><td>Deletes existing binaries, executables, libraries, tests, and <br/>samples.</td></tr>
+ <tr><td>install</td><td>Build the library, executables, and samples, and copy them (along with <br/>the header files)
+ the specified install location.</td></tr>
+ <tr><td>install-package</td><td>Installs the library, executables, and samples to the <br/>specified location.</td></tr>
+ <tr><td>Samples</td><td>Builds the samples.</td></tr>
+ <tr><td>Tests</td><td>Builds the tests.</td></tr>
+ </table>
+ </li>
+</ol>
+<!-- note>To recompile existing applications without changing your source code, be sure to modify the command line in your Makefile
+ to pick up the Xalan headers from it's new location. e.g: if your xalan source location is in /home/&xslt4c-unix_root;,</note>
+<p><br/> <code>CC ... -I/home/&xslt4c-unix_root;/src -I/home/&xslt4c-unix_root;/src/xalanc
+ mysrc.cpp</code></p -->
+</s3>
+
+<anchor name="locale"/>
+<s3 title="Steps for doing a Build with Message Localization Support">
+<p>Message Localization Support is a new feature to allow users to build &xslt4c; such that diagnostic messages are issued
+ in the language of their choice. Message localization support comes in three flavours:</p>
+<ul>
+ <li>Building static messages in the form of a library (DLL or shared object) which can be bound
+ to the Xalan executable. This method is referred to as "in memory". By default, &xslt4c; is built using "in memory"
+ method.</li>
+ <li>Building messages in the form of a library using localization support provided by the International Components for
+ Unicode (ICU). </li>
+ <li>Building messages in the form of a message catalog. This method utilizes the localization support provided by the Unix
+ National Language Support (NLS) system. This method is supported for UNIX platforms only. </li>
+</ul>
+<p>Regardless of which method you choose, a message file containing translated messages in the language of your choice must
+ be provided. The standard message file provided in the &xslt4c-current; source package is in XML Localization Interchange
+ File Format (XLIFF) format and conforms to the XLIFF 1.1 standard (please see
+ <jump href="http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm">
+ http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm</jump> for more information.) All message files
+ must be written and conform with the XLIFF 1.1 standard.</p>
+<p>Once an XLIFF message file has been created, the XLIFF file should be stored under &xslt4c-unix_root;/src/xalanc/NLS/<locale_name>
+ directory (for example, the default XLIFF message file provided is XalanMsg_en_US.xlf). To build, you will need to follow the
+ same steps as shown above for building in Unix or Windows but with a small change.</p>
+<p>For building on Windows platform with "In Memory" method:</p>
+<ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to the root directory of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the ICU root directory.</li>
+ <li>Open the Xalan.dsw workspace using Microsoft Visual C++. The "inmem" localization method should be configured by default.</li>
+ <li>Select the Localization project, and go to Settings and click on the "General" tab. Verify
+ the build command line to use "nmake /f BuildMessages.mak TYPE=inmem LOCAL=en_US"</li>
+ <li>Run "Build all" with the configuration of your choice. </li>
+</ol>
+<p>For building on the Windows platform with ICU method:</p>
+<ol>
+ <li>Create the environment variable XERCESCROOT and set it to the path to the root directory of &xml4c;.</li>
+ <li>Create the environment variable ICUROOT and set it to the path to the ICU root directory.</li>
+ <li>Open the XalanICU.dsw workspace using Microsoft Visual C++. </li>
+ <li>Select the AllInOneWithICU project, and ensure that the project depends on the LocalizationWithICU
+ project. </li>
+ <li>Select the LocalizationWithICU project, and go to Settings and click on the "General" tab. Modify
+ the build command line to use "nmake /f BuildMessages.mak TYPE=icu LOCAL=en_US"</li>
+ <li>Open the tools.ini file under Projects\Win32\VC6\Utils\Localization and add the ICU root
+ directory to the ICUROOT variable setting.</li>
+ <li>Run "Build all" with the configuration of your choice. </li>
+</ol>
+<p>For building on the Unix platform:</p>
+<ol>
+ <li>Repeat steps 1 through 5 as outlined under "Steps for doing a UNIX Build" </li>
+ <li>Run the runConfigure and provide the platform, C compiler, C++ compiler, the message locale
+ system flavour you are intending to build, and the locale support.<br/><br/>
+ Example 1: to use the NLS method for localization support using the default locale en_US:<br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC -m nls</code><br/><br/>
+ <ref>AIX (64-bit):</ref> .<code>/runConfigure -p aix -c xlc_r -x xlC_r -b 64 -m nls</code><br/><br/>
+ Example 2: to use the 'icu' method for localization support using the locale fr_FR:<br/><br/>
+ <ref>AIX (32-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -m icu -M fr_Fr</code><br/><br/>
+ <ref>AIX (64-bit):</ref> <code>./runConfigure -p aix -c xlc_r -x xlC_r -b 64 -m icu -M fr_Fr</code><br/><br/>
+ </li>
+ <li>Perform steps 7 and 8 as outlined under "Steps for doing a UNIX Build" </li>
+</ol>
+<p>After &xslt4c; and associated libraries have been successfully built, the message catalog will be stored in the directory
+ &xslt4c-unix_root;/bin.<br/><br/>
+<table>
+ <tr><th>Localization Build Type</th><th>File Name</th></tr>
+ <tr><td><ref>ICU or "in memory" method:</ref></td><td>&xslt4c-msgsho; (for UNIX)<br/>
+ &xslt4c-msgdll; and &xslt4c-msglib; (for Windows)</td></tr>
+ <tr><td><ref>NLS method:</ref></td><td>&xslt4c-msgcat; can be found in $XALANCROOT/nls/<locale_name>/ directory</td></tr>
+</table>
+</p>
+<p>The location of the message library, &xslt4c; and &xml4c; binaries need to be added to the PATH and library path variables.
+ Depending on the Message Localization Support method you've chosen, the following steps will need to be performed such that
+ &xslt4c; will be able to utilize the message library. </p>
+<ul>
+ <li>For an "in memory" or "icu" build, the location of the &xslt4c; and &xml4c; executables need to be added to the PATH variable.
+ The location of the message library will need to be added to:
+ <ul>
+ <li>the LIBPATH variable for AIX users </li>
+ <li>the LD_LIBRARY_PATH variable for RedHat, SuSE, and Solaris users </li>
+ <li>the SHLIB_PATH variable for HP-UX users. </li>
+ </ul>
+ </li>
+ <li>For an NLS build, the message catalog will need to be added to the NLSPATH. </li>
+</ul>
+</s3>
+
+<!--
+<anchor name="xercesdepdom"/>
+<s3 title="Steps for doing a Build with Xerces Deprecated DOM Support">
+<p>If your application is dependent on the XercesBridge classes to interface with the deprecated Xerces DOM, then the following
+ steps must be taken.</p>
+<p>For a Windows build using Microsoft Visual C++ version 6.0:</p>
+<ol>
+ <li>Open the Xalan.dsw workspace</li>
+ <li>Go to "Projects" and select "Settings". From the "Project Settings panel", highlight the AllInOne project.</li>
+ <li>Click on the "C/C++" tab on the right hand side. From the "Category" pull down menu, scroll down to find "Preprocessor"
+ and click to highlight this category.</li>
+ <li>Under the "Preprocessor Definitions" box, add "XALAN_BUILD_DEPRECATED_DOM_BRIDGE" to the list of definitions.</li>
+ <li>Rebuild &xslt4c; as described under <link anchor="win32">"Steps for doing a Windows Build"</link></li>
+</ol>
+<p>For a UNIX build, the following parameter should be added to your runConfigure step: <code>-z -DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code>.
+ For example,</p>
+ <code>./runConfigure -p aix -c xlc_r -x xlC_r -z -DXALAN_BUILD_DEPRECATED_DOM_BRIDGE</code><br/><br/>
+</s3>
+-->
+
+</s1>
Added: xalan/c/trunk/xdocs/sources/xalan/builddocs.xml
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/builddocs.xml?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/builddocs.xml (added)
+++ xalan/c/trunk/xdocs/sources/xalan/builddocs.xml Sat Jun 16 04:28:14 2012
@@ -0,0 +1,328 @@
+<?xml version="1.0" standalone="no"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
+<s1 title="Building The Documents">
+
+<ul>
+<li><link anchor="buildweb">Building the Xalan-C Web Pages</link></li>
+ <ul>
+ <li><link anchor="b_web_1">Documentation Source Tree</link></li>
+ <li><link anchor="b_web_2">Destination Build Tree</link></li>
+ <li><link anchor="b_web_3">The Web Page Build Environment</link></li>
+ <li><link anchor="b_web_4">Preparing the Navigation File</link></li>
+ <li><link anchor="b_web_5">Creating the Web Pages</link></li>
+ </ul>
+<li><link anchor="buildapi">Building the Xalan-C API Reference</link></li>
+ <ul>
+ <li><link anchor="b_api_1">API Configuration Source Tree</link></li>
+ <li><link anchor="b_api_2">Destination Path for API Web Pages</link></li>
+ <li><link anchor="b_api_3">Build the API Web Pages</link></li>
+ </ul>
+<li><link anchor="integrateapi">Integrate API With Xalan-C Project Web Pages</link></li>
+</ul>
+
+<anchor name="buildweb"/>
+<s2 title="Building the Xalan-C Web Pages">
+
+<p>This section shows how to build the documentation products for Xalan-C/C++.
+This is a subproject of the ASF XALAN PMC.
+</p>
+<p>The XALAN PMC project web page [<jump
+href="http://xalan.apache.org">http://xalan.apache.org</jump>] is a top-level page
+with branches to the subprojects that include the Java and C/C++ code libraries.
+</p>
+<p>The Xalan-C/C++ home web page [<jump
+href="http://xml.apache.org/xalan-c">http://xml.apache.org/xalan-c</jump>]
+is the content
+construction that is being described here.
+</p>
+<p>The Apache StyleBook Java program is no longer needed to create useful web pages.
+You should have a standard XSLT transform utility.
+The "Xalan" command-line program distributed with Xalan-C works just fine.
+</p>
+
+<anchor name="b_web_1"/>
+<s3 title="Documentation Source Tree">
+
+<source>
+xalan/c/trunk/xdocs/sources/
+ entities.ent -- Product specific entities
+ make-book.bat -- Build All Web Pages
+ make-xalan.bat -- Build Single Web Page
+ xalan-book.xslt -- Transformation for StyleBook XML
+ xalan.xml -- The Navigation Panel for Xalan-C Pages
+
+xalan/c/trunk/xdocs/sources/xslt-resources/
+ {Common components used by Xalan-C Web Pages}
+ apache-xalan.css -- The Web Page Presentation Style
+ asf_logo.png -- The ASF Trademark Logo
+ note.gif -- A (note:) graphic
+
+xalan/c/trunk/xdocs/sources/xalan/
+ {The StyleBook XML Sources for Xalan-C Web Pages}
+ index.xml -- This creates the root index.html
+ resources.xml -- A resources dispatch page
+
+xalan/c/trunk/xdocs/style/dtd/
+ {Resources for Apache StyleBook Validation}
+ blocks.ent
+ book.dtd
+ changes.dtd
+ characters.ent
+ document.dtd
+ faqs.dtd
+ links.ent
+ markup.ent
+</source>
+</s3>
+
+<anchor name="b_web_2"/>
+<s3 title="Destination Build Tree">
+
+<source>
+xalan/c/trunk/build/docs/html/
+ {The Xalan-C project html Web Pages go here}
+ index.html -- This is the root of the Xalan-C subproject
+
+xalan/c/trunk/build/docs/html/resources/
+ {Resources to support Xalan-C project html Web Pages}
+ apache-xalan.css
+ asf_logo.png
+ note.gif
+
+xalan/c/trunk/build/docs/html/apiDocs/
+ {The Xalan-C API Web Pages go here}
+ index.html -- This is the root of the Xalan-C API Documents
+</source>
+</s3>
+
+<anchor name="b_web_3"/>
+<s3 title="The Web Page Build Environment">
+
+<p>The examples here describe how to build the Xalan-C/C++ web pages when
+connected to the a copy of the (xdocs/sources) directory. So connect to it.
+</p>
+<p>The StyleBook DTD validation files are in the (xdocs/style/dtd) directory.
+</p>
+<p>The StyleBook XML sources for the web pages are in the (xdocs/sources/xalan) directory. Each web page is associated with an XML file in this directory. The transformed output is to be placed in the (build/docs/html) directory. The source XML file and the destination HTML file have the same base filename.
+</p>
+<p>The Web Page output directory is (build/docs/html).
+</p>
+<p>After creating the web pages, copy the (xdocs/sources/xslt-resources/*) files to the (build/docs/html/resources) directory.
+</p>
+<p>Graphic images for individual web pages are in the (xdocs/xalan-graphic) directory and later copied to the (build/docs/html) directory.
+</p>
+</s3>
+
+<anchor name="b_web_4"/>
+<s3 title="Preparing the Navigation File">
+
+<p>The (xdocs/sources/xalan.xml) is the project navigation file that is on
+the left side of each web page.
+The root element is <book>
+containing child elements of <hidden>, <external>,
+<document>, <resources>, <faqs>, and <separator>. The format of this navigation file is inherited from the StyleBook Java program. Our stylesheet uses the <book> to provide only a navigation panel. It does not control the production of the entire suite of web pages.
+</p>
+<p>The markup is validated by DTD and entity definitions in the (xdocs/style/dtd) directory.
+</p>
+<p>The "id=" attribute is the name of the web page file without extension.
+</p>
+<p>The "label=" attribute is the navigation text.
+</p>
+<p>The "source=" attribute is the name of the StyleBook XML source file.
+</p>
+<p>The "href=" attribute is a link to an external resource.
+</p>
+</s3>
+
+<anchor name="b_web_5"/>
+<s3 title="Creating the Web Pages">
+
+<p>The XSLT transformation utility must support top-level parameters.
+The <code>Xalan</code> command-line program built and distributed with the this project
+has sufficient capability to create the project web pages.
+The <code>xalan-book.xslt</code> stylesheet is designed to interpret StyleBook XML and create XHTML web pages for the Xalan-C project.
+</p>
+<p>Example: Create the <code>index.html</code> web page from <code>index.xml</code> source. The arguments are shown on separate lines for convenience of presentation.
+</p>
+<source>
+Xalan.exe
+ -p sectionid "'index'"
+ -p createdate "'Tue 08/09/2011'"
+ xalan\index.xml
+ xalan-book.xslt
+ > ..\..\build\docs\html\index.html
+</source>
+
+<p>Do the same for each web page replacing <code>index</code>,
+<code>index.xml</code>, and <code>index.html</code> in the above example.
+</p>
+<p>Other command-line XSLT processors would have a different calling syntax.
+Check your documentation.</p>
+<p>I use batch files or shell scripts to automate this process.
+The following batch files are what I use on Windows platforms.
+</p>
+<p>The <code>make-book.bat</code> file is used to create all web pages:
+</p>
+<source>
+ mkdir ..\..\build\docs\html\resources
+
+ call make-xalan usagepatterns
+ call make-xalan samples
+ call make-xalan resources
+ call make-xalan install
+ call make-xalan download
+ call make-xalan overview
+ call make-xalan charter
+ call make-xalan whatsnew
+ call make-xalan extensionslib
+ call make-xalan commandline
+ call make-xalan readme
+ call make-xalan releasenotes
+ call make-xalan programming
+ call make-xalan getstarted
+ call make-xalan index
+ call make-xalan extensions
+ call make-xalan faq
+ call make-xalan license
+ call make-xalan buildlibs
+ call make-xalan secureweb
+
+ copy xalan-graphic\*.* ..\..\build\docs\html
+ copy xslt-resources\*.* ..\..\build\docs\html\resources
+</source>
+
+<p>The <code>make-xalan.bat</code> file to create a single web page:
+</p>
+<source>
+ ::
+ :: Set the current path to include a stylesheet transformation utility
+ ::
+ :: %1 The document filename (without extension) to transform
+ ::
+ :: %XALANEXSLT% The exslt stylesheet transformation utility
+ ::
+ :: %XALANSTYLE% The XSLT stylesheet to convert STYLEBOOK markup
+ ::
+ :: %XALANXMLDIR% Source directory of STYLEBOOK markup XML documents
+ ::
+ :: %XALANOUTDIR% Target directory of XHTML web page documents
+ ::
+ :: %WEBCREATED% Web Page Creation Date
+ ::
+ :: sectionid Top-level stylesheet parameter (document file id)
+ ::
+ :: createdate Top-level stylesheet parameter (web page creation date)
+ ::
+
+ SET WEBCREATED=%DATE%
+ SET XALANEXSLT=..\..\bin\xalan.exe
+ SET XALANSTYLE=xalan-book.xslt
+ SET XALANXMLDIR=xalan
+ SET XALANOUTDIR=..\..\build\docs\html
+
+ "%XALANEXSLT%" -p sectionid "'%1'" -p createdate "'%WEBCREATED%'" \
+ %XALANXMLDIR%\%1.xml %XALANSTYLE% >% XALANOUTDIR%\%1.html
+</source>
+</s3>
+</s2>
+
+<anchor name="buildapi"/>
+<s2 title="Building the Xalan-C API Reference">
+
+<p>This section shows how to build the Xalan-C/C++ application program interface (API) documents using the <jump href="http://www.doxygen.org">Doxygen</jump> and
+<jump href="http://www.graphviz.org">GraphViz</jump> programs. These required software packages are available for most Unix systems.
+</p>
+
+<anchor name="b_api_1"/>
+<s3 title="API Configuration Source Tree">
+
+<source>
+xalan/c/trunk/src/xalanc/ -- [*.h, *.hpp] source code files
+
+xalan/c/trunk/xdocs/
+ DoxyfileXalan -- The doxygen configuration file
+
+xalan/c/trunk/xdocs/html/apiDocs/
+ asf_logo_wide.gif -- The wide ASF trademark logo
+ footer.html -- The footer html fragment for copyright
+ header.html -- Header html fragment for document title
+ header-local.html -- Header html fragment for optional title
+</source>
+
+<p>Note: (ApacheLogo.jpg) is replaced with (asf_logo_wide.gif).
+</p>
+<p>Note: (diagramnotes.html) is replaced with (graph_legend.html) created by doxygen.
+</p>
+</s3>
+
+<anchor name="b_api_2"/>
+<s3 title="Destination Path for API Web Pages">
+
+<p>The Xalan-C/C++ API pages are constructed here.</p>
+<source>
+ xalan/c/trunk/build/docs/apiDocs/html
+</source>
+</s3>
+
+<anchor name="b_api_3"/>
+<s3 title="Build the API Web Pages">
+
+<p>You must have usable "doxygen" and "dot" programs in your path. The "dot" program is part of the GraphViz distribution.
+</p>
+<p>Connect to your development sources or SVN snapshot.<br/>
+<source>
+xalan/c/trunk/xdocs/
+</source>
+Run the doxygen (or doxywizard) program.<br/>
+<source>
+doxygen DoxyfileXalan 2>errors.log | tee doxygen.log
+</source>
+Examine the (errors.log) file for any fatal errors. Lots of warnings are ok.
+You can examine the constructed web pages with your favorite browser.<br/>
+<source>
+% cd xalan/c/trunk/build/docs/apiDocs/html
+% iceweasel index.html &
+</source>
+</p>
+</s3>
+</s2>
+
+<anchor name="integrateapi"/>
+<s2 title="Integrate API With Xalan-C Project Web Pages">
+
+<p>Copy the contents of <br/>
+<source>
+xalan/c/trunk/build/docs/apiDocs/html/*
+</source>
+to the Xalan-C Project Web Pages found at <br/>
+<source>xalan/c/trunk/build/docs/html/apiDocs/
+</source>
+Copy the trademark logo <br/>
+<source>
+xalan/c/trunk/xdocs/html/apiDocs/asf_logo_wide.gif
+</source>
+to its final resting place <br/>
+<source>
+xalan/c/trunk/build/docs/html/apiDocs/
+</source>
+</p>
+</s2>
+</s1>
Added: xalan/c/trunk/xdocs/sources/xalan/buildlibs.xml
URL: http://svn.apache.org/viewvc/xalan/c/trunk/xdocs/sources/xalan/buildlibs.xml?rev=1350859&view=auto
==============================================================================
--- xalan/c/trunk/xdocs/sources/xalan/buildlibs.xml (added)
+++ xalan/c/trunk/xdocs/sources/xalan/buildlibs.xml Sat Jun 16 04:28:14 2012
@@ -0,0 +1,525 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+
+<s1 title="Building Xalan-C/C++">
+<ul>
+<li><link anchor="winbldenv">Windows Build Environment</link></li>
+<ul>
+<li><link anchor="winbld">Windows Basic Build Instruction</link></li>
+<li><link anchor="winbldcmd">Sample Windows Build Command File</link></li>
+<li><link anchor="winbldinst">Installing the Xalan Library on Windows</link></li>
+</ul>
+<li><link anchor="unixbldenv">UNIX Build Environment</link></li>
+<ul>
+<li><link anchor="unixlibpath">Finding Runtime Libraries</link></li>
+<li><link anchor="unixbldxalan">Building the Xalan-C/C++ XSLT Libraries for UNIX</link></li>
+</ul>
+<li><link anchor="unixcompileref">Reference on Unix Platforms and C++ Compilers</link></li>
+<li><link anchor="xercesmodules">Xerces-C/C++ Transcoders and Plug-in Modules</link></li>
+<!-- <li><link anchor=""></link></li> -->
+</ul>
+
+<br/>
+<p>The Xalan-C/C++ XSLT library is built upon the Xerces-C/C++ XML Parser library. Before compiling the Xalan-C/C++ XSLT library, you must have a usable Xerces-C/C++ library.
+</p>
+<p>You can either install a compatible binary distribution of Xerces-C/C++ or build your own from a source distribution of Xerces-C/C++. You can gain additional capability if you build the Xerces-C/C++ XML Parser library from sources. The Xerces-C/C++ binary distribution is not built for the IBM-ICU libraries. The IBM-ICU libraries provide additional transcoding services.
+</p>
+<p>Building the source code packages ensures that the resulting packages are proper for your system. There are various binary distributions available, but incompatibilities between C++ compilers (even between compiler versions) are known to cause issues with sharing of libraries.
+</p>
+<p>We don't have persons yet committed to build binary distribution releases.
+</p>
+<p>You can get more information on the Xerces-C/C++ distributions at the <jump href="http://xml.apache.org/xerces-c">http://xml.apache.org/xerces-c</jump> web site.
+</p>
+
+<anchor name="winbldenv"/>
+<s2 title="Windows Build Environment">
+
+<p>Build support for Microsoft Visual Studio (VC6) is deprecated.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio (VC6) requires the Xerces-C/C++ version 2.8 or older releases. Microsoft VC6 is removed from the Xerces-C/C++ Version 3.x releases.
+</p>
+<p>Building Xalan-C/C++ with Microsoft Visual Studio .NET 2008 (VC9) requires Xerces-C/C++ version 3.1 or newer. Building with Microsoft Visual Studio .NET 2010 (VC10) requires Xerces-C/C++ version 3.1.1 or newer.
+</p>
+<p>Environment variables XERCESCROOT and XALANCROOT are required. Environment ICUROOT is used only if building Xalan-C/C++ with IBM-ICU library support.
+</p>
+<table>
+<tr>
+ <td><en>XERCESCROOT</en></td><td>The Xerces-C/C++ installation directory</td>
+</tr>
+<tr>
+ <td><en>XALANCROOT</en></td><td>The Xalan-C/C++ source directory</td>
+</tr>
+<tr>
+ <td><en>ICUROOT</en></td><td>The IBM-ICU installation directory (only if building with ICU support)</td>
+</tr>
+</table>
+
+<p>I like to create command or batch files to setup the build environment variables and start the Visual Studio .NET development system using the custom build environment. I find this much easier than navigating the graphical interface to add custom build environments. The Microsoft *.vsprops custom property files are not available in the early versions of Visual Studio .NET platforms.
+</p>
+<anchor name="winbld"/>
+<s3 title="Windows Basic Build Instruction">
+<p>If you want to create binary packages from the sources, you may wish to look
+at the <link anchor="winbldcmd">Windows Build Command File</link> in the next section.
+</p>
+<p>A quick experiment in building for Windows is documented in the remainder of this section.
+</p>
+<p>I have Visual Studio 2005, 2008, 2010 on one computer and VC6 and Visual Studio 2003
+installed on another computer.
+</p>
+<p>Microsoft Visual Studio .NET products will usually install
+a Visual Studio Command Prompt icon in the Visual Studio Tools subfolder
+for each version of Visual Studio installed on your computer.
+The Visual Studio Command Prompt automatically sets a basic development environment
+using a "vsvars32.bat" or "vcvarsall.bat" script
+for 32-bit or 64-bit platform builds, and leaves you at the command line for
+customizing your environment.
+</p>
+<p>You then define the XERCESCROOT, XALANCROOT, and ICUROOT environment variables.
+</p>
+<p>If the Xerces-C DLL files are not in directory %XERCESCROOT%\bin, you must add
+a directory to the PATH environment variable so the Xerces-C DLL files can be
+found.
+</p>
+<p>You then launch the Visual Studio .NET by calling <code>devenv</code> with a
+path to the <code>Xalan.sln</code> file as a parameter.
+</p>
+<p>The following section describes how you can build your own scripts to create
+binary packages from Xalan-C compiled sources for the various versions of
+Microsoft Visual Studio products.
+</p>
+</s3>
+<anchor name="winbldcmd"/>
+<s3 title="Sample Windows Build Command File">
+
+<p>I like to use this template for both Xerces-C and Xalan-C builds from sources. The sample shown here is for Xalan-C/C++ because the installation of Xerces-C/C++ should already have been done.
+</p>
+<source>
+SET XERCESCROOT="path to xerces-c installation"
+SET XALANCROOT="sources\xalan\c\"
+</source>
+<p>Set the xalan project path for your version of Microsoft Visual Studio .NET.
+</p>
+<source>
+:: VS 2003 (VC7.1)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC10
+</source>
+<p>Set some environment variables so we can easily copy or install the products after they have been built.
+</p>
+<source>
+:: VS 2003 (VC7.1)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC7.1
+
+:: VS 2005 (VC8)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC8
+
+:: VS 2008 (VC9)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC9
+
+:: VS 2010 (VC10)
+SET XALANCBUILDDIR=%XALANCROOT%\Build\Win32\VC10
+</source>
+<p>We use this Visual Studio .NET solution file.
+</p>
+<source>
+SET XALANCBUILDSLN=%XALANCPROJDIR%\xalan.sln
+</source>
+<p>The <code>$(variable)</code> is expanded inside Visual Studio.<br/>
+The <code>%variable%</code> is expanded by the cmd utility before launching the Visual Studio.
+</p>
+<source>
+SET PATH=%WINDIR%\system32;%WINDIR%;%WINDIR%\system32\Wbem
+SET INCLUDE=
+SET LIB=
+SET LIBPATH=
+SET SOURCE=
+</source>
+<p>Set the default environment variables for your version of Microsoft Visual Studio .NET.
+</p>
+<source>
+:: VS 2000 (VC7) - obsolete
+call "%VS70COMNTOOLS%vsvars32.bat"
+
+:: VS 2003 (VC7.1) 32-bit platform
+call "%VS71COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 32-bit platform
+call "%VS80COMNTOOLS%vsvars32.bat"
+
+:: VS 2005 (VC8) 64-bit platform
+call "%VS80COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2008 (VC9) 32-bit platform
+call "%VS90COMNTOOLS%vsvars32.bat"
+
+:: VS 2008 (VC9) 64-bit platform
+call "%VS90COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+
+:: VS 2010 (VC10) 32-bit platform
+call "%VS100COMNTOOLS%vsvars32.bat"
+
+:: VS 2010 (VC10) 64-bit platform
+call "%VS100COMNTOOLS%\..\..\VC\vcvarsall.bat" x86_amd64
+</source>
+<p>The LIBPATH and SOURCE environment variables may not be properly
+set by the vsvars32.bat command file. You may wish to start your
+Visual Studio .NET application without any custom environment
+and examine the Tools -> C/C++ project defaults for the various libraries.
+Then specifically set the paths in the build command file for your project.
+</p>
+<p>The Xalan-C and Xerces-C libraries do not use the Microsoft Framework,
+the "mfc" and the "atl" directives. Microsoft is deprecating their "mfc"
+Microsoft Foundation Classes.
+</p>
+<p>Define the necessary environment variables for building the Xalan-C/C++ libraries and sample programs.
+</p>
+<source>
+SET PATH=%PATH%;%XERCESCROOT%\bin
+
+SET INCLUDE=%INCLUDE%;%XERCESCROOT%\include;%XERCESCROOT%\src
+SET INCLUDE=%INCLUDE%;%XALANCROOT%\src
+
+SET LIB=%LIB%;%XERCESCROOT%\lib
+</source>
+<p>If you are going to build for IBM-ICU support, then add the following environments.
+</p>
+<source>
+SET ICUROOT="path to ibm-icu installation"
+
+SET PATH=%PATH%;%ICUROOT%\bin
+SET INCLUDE=%INCLUDE%;%ICUROOT%\include
+SET LIB=%LIB%;%ICUROOT%\lib;%ICUROOT%\data
+</source>
+<p>Now we should be ready to start the Microsoft Visual Studio .NET using our custom environment using the <code>%XALANCBUILDSLN%</code> solution.
+</p>
+<source>
+devenv.exe "%XALANCBUILDSLN%" /useenv
+</source>
+</s3>
+<anchor name="winbldinst"/>
+<s3 title="Installing the Xalan Library on Windows">
+
+<p>The following command script will install the binary and header files to a target directory that is compatible with the XALANCROOT environment variable for creating applications. Environment variables other than XALANCTARGET are defined in the previous section, the <link anchor="winbldcmd">Visual Studio .NET build example</link>.
+</p>
+<source>
+SET XALANCTARGET="path-to-target-directory"
+
+MKDIR "%XALANCTARGET%\bin"
+MKDIR "%XALANCTARGET%\include"
+MKDIR "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Release\Nls"
+COPY *.hpp "%XALANCTARGET%"\include
+
+CD "%XALANCBUILDDIR%\Release"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCBUILDDIR%\Debug"
+COPY *.DLL "%XALANCTARGET%\bin"
+COPY *.PDB "%XALANCTARGET%\bin"
+COPY *.LIB "%XALANCTARGET%\lib"
+COPY *.EXP "%XALANCTARGET%\lib"
+
+CD "%XALANCROOT%\src
+XCOPY xalanc\*.hpp "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+XCOPY xalanc\*.h "%XALANCTARGET%\include\xalanc" /E /C /I /R /Y
+</source>
+</s3></s2>
+<anchor name="unixbldenv"/>
+<s2 title="UNIX Build Environment">
+
+<p>I don't like building sources using root or superuser login. I like to do builds in a directory separated from the source tree. A debug build and release build will create shared objects of the same name. I like to target these builds to separate directory trees.
+</p>
+<p>Release builds are targeted at the <code>/usr/local</code> file system.
+</p>
+<p>Debug builds are targeted at the <code>/opt/apache/debug</code> file system.
+</p>
+<p>Source trees are referenced wherever convenient. Using the (<code>--srcdir</code>) configuration parameter allows the source tree to be separate from the build tree. The source tree can even reside on read-only media.
+</p>
+<p>Product builds are done in a build directory path separate from the source tree. This is the working directory from where you perform your builds and installs.
+</p>
+<p><em>Source Trees:</em> (<code>--srcdir</code>) configuration parameter
+</p>
+<p>
+ <code>/opt/xerces/c/<trunk>/</code><the Xerces-C/C++ XML parser library source distribution>
+<br/>
+ <code>/opt/xalan/c/<trunk></code>/<the Xalan-C/C++ XSLT library source distribution>
+</p>
+<p>If the source distribution is well-constructed, the source directory trees can be read-only.
+</p>
+<p><em>Binary Installation Trees:</em> (<code>--prefix</code>) configuration parameter
+</p>
+<p>
+ <code>/usr/local/</code> <the target for the
+release binary installation>
+<br/>
+ <code>./bin</code> The sample programs
+<br/>
+ <code>./lib</code> The shared and static library files
+<br/>
+ <code>./include</code> The library header files
+<br/>
+<br/>
+ <code>/opt/apache/debug/</code> <the target for the
+debug binary installation>
+<br/>
+ <code>./bin</code> The sample programs
+<br/>
+ <code>./lib</code> The shared and static library files
+<br/>
+ <code>./include</code> The library header files
+</p>
+
+<p>The default (<code>--prefix</code>) value is <code>/usr/local</code> which I use for release builds.
+</p>
+<p>I choose (<code>--prefix</code>) value of <code>/opt/apache/debug</code> for debug builds.
+</p>
+
+<p><em>Build Tree:</em> The build working directory tree
+</p>
+<p> <code>/<user-directory>/Build/</code>
+</p>
+
+<p>You can use any empty file system or directory path with write access. Starting with an empty directory is a quick way to do a clean build. Make this empty directory to be your current working directory.
+</p>
+<p>I also like to make some shell scripts so that the build process can be automated. I locate these scripts outside of the Build directory so they don't get lost when I purge directory content.
+</p>
+<p>
+ <code>../build-xerces-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-lib.sh</code>
+</p>
+<p>
+ <code>../build-xalan-app.sh</code>
+</p>
+<p>I generate these shell scripts with a text editor and use them to minimize keyboard typing errors.
+</p>
+<anchor name="unixlibpath"/>
+<s3 title="Finding Runtime Libraries">
+
+<p>The various types of UNIX operating systems have differing requirements for finding libraries at runtime.
+</p>
+<table>
+<tr><th>Operating System</th><th>Library Path Environment</th></tr>
+<tr><td>Solaris and Linux</td><td>LD_LIBRARY_PATH</td></tr>
+<tr><td>HP-UX</td><td>SHLIB_PATH</td></tr>
+<tr><td>AIX and BSD</td><td>LIBPATH</td></tr>
+<tr><td>Mac OS X</td><td>DYLD_LIBRARY_PATH</td></tr>
+<tr><td>Cygwin and MinGW</td><td>PATH</td></tr>
+</table>
+
+<p>The Xalan-C/C++ and Xerces-C/C++ shared library objects must be installed in a reachable library path for your platform. The <code>make</code> step creates the libraries in the <code>lib</code> subdirectory of your working directory. The <code>make install</code> step installs these shared objects to the designated <code>{prefix}/lib</code> directory or another directory defined by the <code>--libdir</code> configuration parameter.
+</p>
+<p>In many cases, the <code>/usr/local/lib</code> is already cached in <code>/etc/ld.so.cache</code> or included by <code>/etc/ld.so.conf</code>. The library path environment variable is then used for exceptions. The explicit library path environment variable usually takes precedence over the other methods of finding shared library runtimes. This is useful if you wish to use a debug environment on the same platform that also includes release libraries of the same name.
+</p>
+</s3>
+
+<anchor name="unixbldxalan"/>
+<s3 title="Building the Xalan-C/C++ XSLT Libraries for UNIX">
+
+
+<p>I don't like building sources from a root or superuser login. I also like to do builds in a directory separated from the source tree.
+</p>
+
+<p>If your sources tree is read-only and some required files are not executable, then you need to copy the source to writable media and change the execute attributes of specific files. This command sequence will copy an entire directory tree from <code>{source-dir}</code> to <code>{dest-dir}</code>.
+</p>
+<source>
+ cd {source-dir}
+ find . | cpio -pdmuv {dest-dir}
+</source>
+<p>Connect to the <code>{xalan-src}</code> directory and make specific files executable.
+</p>
+<source>
+ cd {xalan-src}
+ chmod 755 runConfigure configure install-sh
+</source>
+<p>Connect to your empty build directory and construct a script for building the Xalan-C/C++ XSLT products.
+</p>
+
+<p>The Xalan-C/C++ configuration process uses the <code>runConfigure</code> script as a front-end to the automake <code>configure</code> script. Your shell command script should therefore use the <code>runConfigure</code> script.
+</p>
+
+<table>
+<tr><th colspan="2">runConfigure Options</th></tr>
+<tr><th>Option</th><th>Description</th></tr>
+<tr><td>-p</td><td>Build platform: aix, linux, freebsd, netbsd, solaris, hp-10, hp-11, hp11-ia64,
+ irix, tru64, macosx, cygwin</td></tr>
+<tr><td>-c</td><td>C compiler name: gcc, cc, c89, xlc, xlc_r, acc (default = gcc)</td></tr>
+<tr><td>-x</td><td>C++ compiler name: g++, CC, C89, xlC, xlC_r, aCC (default = g++)</td></tr>
+<tr><td>-d</td><td>Indicates a debug build, takes no values, default is No Debug</td></tr>
+<tr><td>-t</td><td>Transcoder to use: 'icu', (Default is null, the Xerces-C/C++ transcoder)</td></tr>
+<tr><td>-m</td><td>Type of localization support: inmem, icu, nls (default is inmem)</td></tr>
+<tr><td>-M</td><td>Locale for message localization: "en_US"</td></tr>
+<tr><td>-r</td><td>Threads option: pthread, dce (default is pthread)</td></tr>
+<tr><td>-b</td><td>Specify 32 or 64 bit build (Default is 32-bit)<br/>
+ On Linux, the 32/64 build is determined by the compiler, kernel, and glibc.</td></tr>
+<tr><td>-P</td><td>Install root directory: value is assigned to the <code>--prefix</code> configure parameter</td></tr>
+<tr><td>-l</td><td>Extra link options (assigned to <code>LDFLAGS</code>)</td></tr>
+<tr><td>-z</td><td>Extra compiler options (assigned to <code>CFLAGS</code> and <code>CXXFLAGS</code>)</td></tr>
+<tr><td>-C</td><td>Extra configuration options (i.e. <code>--srcdir=${SourceDir}</code>)</td></tr>
+<tr><td>-h</td><td>Print the <code>runConfigure</code> help and exit</td></tr>
+</table>
+
+<p>Here are the names of some C/C++ compilers associated with commercial UNIX operating systems used to build Xalan-C/C++ and Xerces-C/C++ packages.
+</p>
+
+<table>
+<tr><th>System</th><th>Platform</th><th>C Compiler</th><th>C++ Compiler</th><th>Comment</th></tr>
+<tr><td>AIX</td><td>aix</td><td>xlc_r</td><td>xlC_r</td><td>thread support</td></tr>
+<tr><td>AIX</td><td>aix</td><td>xlc</td><td>xlC</td><td>no thread support</td></tr>
+<tr><td>Cygwin</td><td>cygwin</td><td>gcc</td><td>g++</td><td></td></tr>
+<tr><td>HP-UX</td><td>hp-11</td><td>cc</td><td>aCC</td><td></td></tr>
+<tr><td>HP-UX</td><td>hp-11-ia64</td><td>cc</td><td>aCC</td><td></td></tr>
+<tr><td>Solaris</td><td>solaris</td><td>cc</td><td>CC</td><td></td></tr>
+</table>
+
+<p>The following example shows you how to construct a usable script with your favorite text editor.
+</p>
+
+<source>
+#!/bin/sh
+# Script to build and install Xalan-C/C++ products from sources
+
+# The Source and Target Directories for Debug Build
+
+# SourceDir="--srcdir=/opt/xalan/c/trunk"
+# DestDir="--prefix=/opt/apache/debug"
+
+# The Source and Target Directories for Release Build
+
+SourceDir="--srcdir=/opt/xalan/c/trunk"
+DestDir="--prefix=/usr/local"
+
+# The Xerces and Xalan package directories
+
+export XALANCROOT=${SourceDir}
+export XERCESCROOT=${DestDir}
+
+# If compiling with IBM-ICU support, the ICUROOT environment variable
+# needs to be defined to specify where the ICU libraries are installed.
+# Specifically, the following directories are accessed:
+# ${ICUROOT}/lib, ${ICUROOT}/include, ${ICUROOT}/data
+# export ICUROOT=/usr/local
+
+export PATH=$PATH:${SourceDir}
+
+# Debug Configure
+
+# runConfigure -p linux -d -c gcc -x g++ -P "${DestDir}" \
+# -C "--srcdir=${SourceDir}"
+
+# Release Configure
+
+runConfigure -p linux -c gcc -x g++ -P "${DestDir}" \
+ -C "--srcdir=${SourceDir}"
+
+# Connect to configured src subdirectory to build the library without
+# sample programs. If you run make from your build directory, then the
+# library and all sample programs will be built.
+
+cd src
+make clean
+make
+
+# As a user with permissions to write to ${DestDir} install the Xalan-C/C++ products
+# ${DestDir}/bin the Xalan command-line utility and sample programs
+# ${DestDir)/lib the Xalan-C/C++ static and dynamic libraries
+# ${DestDir}/include/xalanc/* The header files.
+
+make install
+
+## End of sample build script.
+</source>
+
+</s3>
+</s2>
+<anchor name="unixcompileref"/>
+<s2 title="Reference on Unix Platforms and C++ Compilers">
+
+<p>Some compilers and platforms may need configuration options and variables that differ from the default Linux build. Beware that the runConfigure script for Xalan-C/C++ is a front-end that calls the configure script. The following table is reference information for the build of Xerces-C/C++ version 3.x. The C++ compiler for Xerces should be the same as used for Xalan builds.
+</p>
+
+<table>
+<tr><th colspan="2">Configuration Options For Unix Platforms</th></tr>
+<tr><th>Solaris x86</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=CC CC=cc</data></td></tr>
+
+<tr><th>Solaris x86-64</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=cc CC=cc CFLAGS=-xarch=amd64 CXXFLAGS=-xarch=amd64</data><br/>
+(newer Sun CC versions use -m64 instead of -arch=amd64)</td></tr>
+
+<tr><th>Solaris Sparc</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=CC CC=cc</data></td></tr>
+
+<tr><th>Solaris Sparc v9</th><th>Sun CC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=cc CC=cc CFLAGS=-xarch=v9 CXXFLAGS=-xarch=v9<br/>
+(newer Sun CC versions use -m64 instead of -arch=v9)</data></td></tr>
+
+<tr><th>AIX PowerPC</th><th>IBM XLC++</th></tr>
+<tr><td colspan="2"><data>./configure CXX=xlc_r CC=xlc_r<br/>
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</data></td></tr>
+
+<tr><th>AIX PowerPC-64</th><th>IBM XLC++</th></tr>
+<tr><td colspan="2"><data>./configure CXX=xlc_r CC=xlc_r CXXFLAGS=-q64 CFLAGS=-q64<br/>
+gmake libxerces_c_1a LDFLAGS=-qmkshrobj</data></td></tr>
+
+<tr><th>HP-UX 1a-64-32</th><th>HP aCC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-mt LDFLAGS=-mt</data></td></tr>
+
+<tr><th>HP-UX 1a-64</th><th>HP aCC</th></tr>
+<tr><td colspan="2"><data>./configure CXX=aCC CC=aCC CFLAGS=-mt CXXFLAGS=-"mt +DD64" LDFLAGS="-mt +DD64"</data></td></tr>
+
+<tr><th>Mac OS X x86-64</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure CFLAGS="-arch x86_64" CXXFLAGS="-arch x86_64"</data></td></tr>
+
+<tr><th>Mac OS X PowerPC-64</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure CFLAGS="-arch ppc64" CXXFLAGS="-arch ppc64"</data></td></tr>
+
+<tr><th>Mac OS X x86/PowerPC</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure --disable-dependency-tracking CFLAGS="arch i386 -arch ppc"<br/>
+CXXFLAGS="-arch i386 -arch ppc"</data></td></tr>
+
+<tr><th>MinGW x86</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure LDFLAGS=-no-undefined</data></td></tr>
+
+<tr><th>Cygwin x86</th><th>GCC</th></tr>
+<tr><td colspan="2"><data>./configure LDFLAGS=-no-undefined</data></td></tr>
+</table>
+</s2>
+
+<anchor name="xercesmodules"/>
+<s2 title="Xerces-C/C++ Transcoders and Plug-in Modules">
+<p>Xerces-C/C++ XML Parsers have undergone some additional modularity features. In the version 3 series, the transcoders are now being implemented as runtime modules. Use of the transcoding modules is still experimental for Xalan-C/C++ transformation applications. The basic transcoder capability still exists. Xerces-C/C++ version 2 series had transcoder libraries explicitly built and installed.
+</p>
+<p>A plug-in memory management architecture was introduced in Xerces-C/C++ version 2.7. The plug-in memory management of Xerces-C/C++ is also supported by Xalan-C/C++ applications.
+</p>
+</s2>
+</s1>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org