dleslie 00/10/03 13:30:28
Modified: c/xdocs/sources/xalan commandline.xml getstarted.xml
readme.xml samples.xml xerces-icu.gif
Log:
Updated refs to build notes and added note on STLPort.
Revision Changes Path
1.11 +9 -18 xml-xalan/c/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- commandline.xml 2000/10/02 12:17:02 1.10
+++ commandline.xml 2000/10/03 20:30:21 1.11
@@ -133,28 +133,19 @@
<li>Uncomment the <code>#define XALAN_USE_ICU</code> in
process.cpp.<br/><br/></li>
<li>Add ICUBridge to the Visual C++ list of dependencies for the
TestXSLT project.<br/><br/></li>
<li>Build TestXSLT.exe.</li>
- </ol>
-
+ </ol>
</s3>
<s3 title="Rebuilding TestXSLT in Linux or AIX">
<p>In Linux and AIX, the ICUBridge is in the core Xalan library
(&xml4c-linuxlib; in Linux; &xml4c-aixlib; in
AIX), so you must rebuild this library along with TestXSLT.</p>
- <ol>
- <li>Define the XALAN_USE_ICU environment variable.<br/>
- The syntax for defining an environment variable depends on the
shell you are using.
- If you are using the Bourne Shell, K Shell, or Bash, use
- <br/><br/> <code>export XALAN_USE_ICU
"1"</code><br/><br/>
- If you are using C Shell, use
- <br/><br/> <code>setenv
XALAN_USE_ICU="1"</code><br/><br/></li>
- <li>Delete the previous build:<br/><br/>
- </li><code> make
clean</code><br/><br/></li>
- <li>Run a complete build<br/><br/>
- <code> make</code></li>
- </ol>
- <note>The make file uses the XALAN_USE_ICU environment variable to
do the equivalent of a #define and to add
- ICUBridge to the list of dependencies for TestXSLT. If you
uncomment the <code>#define XALAN_USE_ICU</code>
- statement in process.cpp (which is the right thing to do in
Windows), you will get a warning about duplicate
- settings when you run the make, and TestXSLT will not link with
ICUBridge.</note>
+ <p>Before you do the build, define the XALAN_USE_ICU environment
variable. For information about defining this
+ environment variable and doing a Linux or AIX build, see <link
idref="readme" anchor="unix">Steps for doing a
+ Linux or AIX build</link>.</p>
+ <note>The make file uses the XALAN_USE_ICU environment variable to do
the equivalent of a #define and to add
+ ICUBridge to the list of dependencies for TestXSLT. If you uncomment
the <code>#define XALAN_USE_ICU</code>
+ statement in process.cpp (which is the right thing to do in Windows),
you will get an error in AIX ("The
+ macro 'XALAN_USER{ICU' has already been defined") and a warning in
Linux about duplicate settings when you
+ run the make, and TextXSLT will not link with ICUBridge.</note>
</s3>
</s2>
</s1>
1.14 +3 -1 xml-xalan/c/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- getstarted.xml 2000/10/02 12:17:04 1.13
+++ getstarted.xml 2000/10/03 20:30:22 1.14
@@ -42,6 +42,8 @@
</ul>
<p>If you want to enable ICU support for the command-line utility, you must
build the ICU and rebuild the Xalan-C++ shared/load library (Linux/AIX) and
TestXSLT (all platforms) with the ICUBridge. See <link idref="usagepatterns"
anchor="icu">Using the ICU</link> and <link idref="commandline"
anchor="icu">Enabling ICU support for TestXSLT</link>.</p>
<p>For information about using the command-line utility, see <link
idref="commandline">Command-Line Utility</link>.</p>
+<note>If you want to do your own AIX build, you must download <resource-ref
idref="stlport"/> and set the STLPORTROOT
+environment variable to the complete path to the STLPort distribution (see
the <link idref="readme" anchor="build">Build notes</link>)</note>
</s3>
<s3 title="What you need to build applications">
<p>To build your own applications with Xalan and Xerces, you also need need
the
@@ -52,7 +54,7 @@
<p>In the AIX distribution (built with the make file and xlC_r), the load
library is in the lib subdirectory.</p>
<p>To get the Xerces-C++ header and (for Windows) .lib files, download and
expand the &xml4c; binary distribution for your platform from the <resource-ref
idref="xml4c-distdir"/>. For information about which &xml4c; distribution has
been tested with this &xslt4c; release, see <link idref="readme"
anchor="status">Version of &xml4c; to use</link>.</p>
<p>If you want to enable ICU support in your applications, you must rebuild
the Xalan-C++ shared/load library (Linux/AIX) and include the ICUBridge headers
(all platforms).</p>
-<p>For information about rebuilding &xslt4c;, see the <link idref="readme"
anchor="build">Build notes</link>.</p>
+<p>For the requirements for rebuilding &xslt4c;, see the <link
idref="readme" anchor="build">Build notes</link>.</p>
</s3>
</s2><anchor name="path"/>
<s2 title="Setting up the path">
1.14 +14 -10 xml-xalan/c/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- readme.xml 2000/10/02 12:17:04 1.13
+++ readme.xml 2000/10/03 20:30:23 1.14
@@ -93,7 +93,7 @@
<ul>
<li><link anchor="layout">Layout of Xerces-C and ICU</link></li>
<li><link anchor="win32">Steps for doing a Windows build</link></li>
- <li><link anchor="linux">Steps for doing a Linux or AIX
build</link></li>
+ <li><link anchor="unix">Steps for doing a Linux or AIX build</link></li>
</ul>
<p>If you want to rebuild &xslt4c; (to produce a debug build, for
example), you need the following:</p>
<ul>
@@ -128,13 +128,14 @@
directory.<br/><br/></li>
<li>(Optional) If you are rebuilding the ICUBridge, install the ICU so
the icu root directory
is at the same level as the xml-xerces root directory (see <link
- idref="usagepatterns" anchor="icu">Using the ICU</link> <br/><br/>
+ idref="usagepatterns" anchor="icu">Using the ICU</link>.<br/><br/>
If you want TestXSLT to use ICU support for number formatting and
sorting, install the ICU,
- uncomment the <code>#define XALAN_USE_ICU</code> statement in
process.cpp, and add ICUBridge to the Visual
- C++ list of TestXSLT dependencies (see <link idref="commandline"
anchor="icu">Enabling ICU support for
- TestXSLT</link>).<br/><br/></li>
+ uncomment the <code>#define XALAN_USE_ICU</code> statement in
process.cpp, and use the Visual C++
+ Project Dependencies command to add ICUBridge to the list of TestXSLT
dependencies (see <link idref="commandline"
+ anchor="icu">Enabling ICU support for TestXSLT</link>).<br/><br/></li>
<li>Use Visual C++ to open the Xalan workspace from the
xml-xalan\c\Projects\Win32\VC6.
<br/><br/></li>
+ <li>Select Project Dependencies and check <br/><br/></li>
<li>Use Visual C++ to rebuild everything or specific dynamic link
libraries and executables of
interest.<br/><br/></li>
</ol>
@@ -147,10 +148,11 @@
<li>Set the XALANCROOT environment variable to the complete path to
the root of the &xslt4c;
distribution.<br/><br/></li>
<li>AIX only: Download <resource-ref idref="stlport"/> and set the
STLPORTROOT environment
- variable to the complete path to the STLPort distribution. The Linux
GNU compiler includes
- the STL (Standard Template Library).<br/><br/></li>
+ variable to the complete path to the STLPort distribution. <br/>
+ (This step is not required for Linux because The Linux GNU compiler
includes the STL (Standard Template
+ Library.)<br/><br/></li>
<li>(Optional) If you are including the ICUBridge, install the ICU
(see <link idref="usagepatterns"
- anchor="icu">Using the ICU</link>)and define
XALAN_USE_ICU.<br/><br/></li>
+ anchor="icu">Using the ICU</link>) and define
XALAN_USE_ICU.<br/><br/></li>
<li>Change directory to xml-xalan/c/src in the &xslt4c;
distribution.<br/><br/></li>
<li>Use the chmod +x command to set the executable flags for conf* and
runConfigure.<br/><br/>
@@ -158,10 +160,12 @@
<code>chmod +x
conf*</code><br/><br/></li>
<li>Run the runConfigure utility with at least the platform flag
(Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated
below.<br/><br/>
<ref>Linux:</ref> <code>runConfigure -p linux</code><br/>
- <ref>AIX:</ref> <code>runConfigure -p aix -c
xlc_r -x xlC-R</code><br/><br/>
+ <ref>AIX:</ref> <code>runConfigure -p aix -c
xlc_r -x xlC_r</code><br/><br/>
To see the other runConfigure flags you may include, use the help
flag:<br/><br/>
<code>runConfigure
-h</code><br/><br/></li>
- <li>Run the make file:<br/><br/>
+ <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/>
1.11 +1 -1 xml-xalan/c/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/c/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- samples.xml 2000/10/02 12:17:05 1.10
+++ samples.xml 2000/10/03 20:30:23 1.11
@@ -83,7 +83,7 @@
modify a .cpp file, you must rebuild the executable and place it on
the path before you can run the
modified application.</li>
</ol>
- <Note> Each sample application looks for input files in the current
directory, the directory from
+ <note> Each sample application looks for input files in the current
directory, the directory from
which you run the application. The input files are in the samples
subdirectory along with the sample source
files. The application executable, on the other hand, is in the build
subdirectory. To run a sample, be sure the
executable is on the path, and run it from the samples subdirectory
that contains the input files.</note>
1.2 +10 -9 xml-xalan/c/xdocs/sources/xalan/xerces-icu.gif
<<Binary file>>
