Release notes for Xalan-C++ version 1.1
| |
| |
Open bugs:
- Does not support 20 or more digits of numerical precision after the decimal.
- The namespace axis does not return the default "xml" namespace.
- Does not support case-order and lang attributes in xsl:sort.
|
|
| |
| |
If you want to rebuild Xalan-C++, you need the following:
- The Xalan-C++ source files
- The Xerces-C++ header and (for Windows) .lib files
- (Optional) The ICU header and (for Windows) .lib files
The Xalan-C++ source files and The required Xerces-C++ files are in the distribution.
For information on using the International Components for Unicode (ICU), see
Using the ICU.
 | If you are not rebuilding with the ICU, you do not need the ICU header or .lib files. |
To rebuild the Windows32 release, use the Microsoft Visual C++ 6.0 project files. To rebuild
the Linux or AIX release, use the make file in the root of the source directory. The builds look
for Xerces-C++ and ICU in directories parallel to the
xml-xalan directory.
|
| |
Important We have set up the Visual C++ projects and the UNIX make files to look for Xerces in the directory structure replicated in our distribution files (see Xalan-C++ Distributions). This matches the structure that results from downloading xml-xerces/c from the Apache XML CVS repository and building with the Visual C++ project files or the UNIX make file.
If you are using a Xerces-C++ binary distribution that you have obtained independently from this Xalan-C++ distribution, you must either modify the Xalan-C++ project files or makefile, or rearrange the build directory structure as indicated in the following illustration.
For UNIX, the XERCESROOT environment variable points to the Xerces-C root directory. For Windows, the Xerces-C root directory must be named xml-xerces, and it must be at the same level as the Xalan-C++ root directory. For all environments, the ICU root directory must be named icu, and it must be at the same level as the Xalan-C++ root directory.
 | Keep in mind that at any given point in time the Xalan-C++ and Xerces-C++ source trees in the Apache XML repository may not be consistent. When we release a version of Xalan-C++ we certify that it is compatible with a given version of Xerces-C++. To be safe, stick with distributions that we certify to be compatible. Reminder: Xalan-C++ version 1.1 is compatible with the Xerces-C++ that is included with the distribution..
Xalan-C++ version 1.1 has been tested with International Components for Unicode(ICU) 1.6 source files. You may be able to use newer ICU releases as they appear. |
|
 |  |  |  | Steps for doing a UNIX build |  |  |  |  |
| |
- Set the XERCESCROOT environment variable to the root of xml-xerces.
- Set the XALANCROOT environment variable to the complete path to the root of the Xalan-C++
distribution.
- AIX and Solaris only: Download STLport and set the STLPORTROOT environment
variable to the complete path to the STLPort distribution.
(This step is not required for Linux or HP-UX 11 because The Linux GNU compiler and HP aCC compiler include the STL (Standard Template
Library.)
- (Optional) If you are including the ICUBridge, install the ICU (see Using the ICU) and use the shell to define XALAN_USE_ICU.
If you are using Bourne Shell, K Shell, or Bash:
export XALAN_USE_ICU "1"
If you are using C Shell:
setenv XALAN_USE_ICU="1"
- Change directory to xml-xalan/c/src in the Xalan-C++ distribution.
- Use the chmod +x command to set the executable flags for conf* and runConfigure.
chmod +x runConfigure
chmod +x conf*
- Run the runConfigure utility with at least the platform flag (Linux) or the platform, C compilier, and C++ compiler flags (AIX) as indicated below.
Linux: runConfigure -p linux
AIX: runConfigure -p aix -c xlc_r -x xlC_r
HP-UX 11: runConfigure -p hp-11 -c cc -x aCC
Solaris: runConfigure -p solaris -c cc -x CC
To see the other runConfigure flags you may include, use the help flag:
runConfigure -h
- Purge the previous build:
make clean
- Run the new build:
make
or
make targ
where targ is ommitted or is all (rebuild all), lib (the XSLT libary), or
TestXSLT (the TestSXSLT executable). ICUBridge is included in the build of TestXSLT if XALAN_USE_ICU is
defined.
 | The command you use for setting environment variables depends on the shell you are
using.
For Bourne Shell, K Shell, or Bash use export ENVAR "val"
For C Shell, use setenv ENVAR="val"
where ENVAR is the environment variable name and val is the environment variable
setting. You can check the setting of an environment variable with echo $ENVAR |
|
 |  |  |  | Rebuilding a sample application |  |  |  |  |
| |
The Windows32 distribution includes a Visual C++ workspace for the sample applications. This workspace is in the samples directory. If you modify a sample and want to recompile it, you can recompile the .cpp file(s) and rebuild the executable.
The make files that come with the UNIX distributions include targets for rebuilding one or all of the sample applications (with the exception of the ThreadSafe sample, which in its current form only runs under Windows). To rebuild one or more sample applications, go to the xml-xalan/c/src directory and run
make targ
where targ is Samples (all the samples), XalanTransform , SimpleTransform , StreamTransform , UseStylesheetParam , TraceListen , CompileStylesheet , (Windows only) ThreadSafe XPathWrapper , ExternalFunctions ,or ApacheModuleXSLT .
|
|
| |
Your feedback is more than welcome. Offers of help are even more so! Perhaps you would like to contribute to the ongoing development, testing, or documentation of Xalan-C++.
Please email your comments, questions, suggestions, bug reports, and offers to help to Xalan Development Mailing List.
|
 |  |  |  | Cumulative history of software changes |  |  |  |  |
| |
|
|