|
|
|
Distributing Xerces-CQuestions
AnswersWhat are the differences between Xerces-C and XML4C?Xerces-C has intrinsic support for ASCII, UTF-8, UTF-16 (Big/Small Endian), UCS4 (Big/Small Endian), EBCDIC code pages IBM037 and IBM1140 encodings, ISO-8859-1 (aka Latin1) and Windows-1252. This means that it can parse input XML files in these above mentioned encodings. However, if you wish to parse XML files in any other encodings, say in Shift-JIS, Big5 etc., then you cannot use Xerces-C. XML4C addresses this need. It combines Xerces-C and International Components for Unicode (ICU) and provides support for over 100 different encodings. ICU is also an open source project but is licensed under the IBM Public License. XML4C is published by IBM and can be downloaded from their Alphaworks site. The license to use XML4C is simply to comply with the Apache license (because of Xerces-C) and IBM Public License (because of ICU). XML4C binaries are published for Solaris using SunWorkshop compiler, HPUX 10.20 and 11.0 using CC and aCC, Redhat Linux using gcc, Windows NT using MSVC, AIX using xlC. Which DLL's do I need to distribute with my application?As mentioned above, there are two configurations in which Xerces-C binaries are shipped. One is from the Apache site, while the other is from IBM published at IBM's Alphaworks Site. If you are using the binaries from the Apache download
site site, then you only need to distribute
one file: However, if you are using the XML4C binaries then in addition to the Xerces-C library file mentioned above, you also need to ship:
How do I package the sources to create a binary drop?You have to first compile the sources inside your IDE to create the required DLLs and EXEs. Then you need to copy over the binaries to another directory for the binary drop. A perl script has been provided to give you a jump start. You need to install perl on your machine for the script to work. If you have changed your source tree, you have to modify the script to suit your current directory structure. To invoke the script, go to the \<Xerces>\scripts directory, and type: perl packageBinaries.pl You will get a message that somewhat looks like this (changes always happpen, we are evolving you see!): Usage is: packageBinaries <options>
options are: -s <source_directory>
-o <target_directory>
-c <C compiler name> (e.g. gcc or xlc_r)
-x <C++ compiler name> (e.g. g++ or xlC_r)
-m <message loader> can be 'inmem', 'icu' or 'iconv'
-n <net accessor> can be 'fileonly' or 'libwww'
-t <transcoder> can be 'icu' or 'native'
-r <thread option> can be 'pthread' or 'dce'
(only used on HP-11)
-h to get help on these commands
Example: perl packageBinaries.pl -s$HOME/xerces-c_1_0_0
-o$HOME/xerces-c_1_0_0
-cgcc -xg++ -minmem
-nfileonly -tnative
Make sure that your compiler can be invoked from the command line and follow the instructions to produce a binary drop. I do not see binaries for my platform. When will they be available?">The reason why you see binaries only for some specific platforms is that we have had the maximum requests for them. Moreover, we have limited resources and hence cannot publish binaries for every platform. If you wish to contribute your time and effort in building binaries for a specific platform/environment then please send a mail to xerces-dev@xml.apache.org. We can definitely use any extra help in this open source project When will a port to my platform be available?We would like to see Xerces ported to as many platforms as there are. Again, due to limited resources we cannot do all the ports. We will help you make this port happen. Here are some Porting Guidelines. We strongly encourage you to submit the changes that are required to make it work on another platform. We will incorporate these changes in the source code base and make them available in the future releases. All porting changes may be sent to: xerces-dev@xml.apache.org . How can I port Xerces to my favourite platform?Some porting information is mentioned on the build page. What application did you used to create the documentation?We have used an internal XML based application to create the documentation. The documentation files are all written in XML and the application, internally codenamed StyleBook, makes use of XSL to transform it into an HTML document that you are seeing right now. It is currently available on the Apache open source website as Cocoon. The API documentation is created using DOC++. Can I get the source code for the C++ Builder TreeViewer application?In view of the numerous requests that we have received for the TreeViewer sample application (written using C++ Builder), we have decided to make it available as an independent download from the IBM AlphaWorks portal. The archive to get from the 'Download' page is 'DOMSampleTreeViewer.zip'. Please note, this is provided on a "as-is, no support" basis. This sample works with XML4C 2.3.1 and we have not verified if it works with XML4C 3.x releases. TreeViewer parses the XML file, using Xerces, and displays the data as a tree. We welcome your additional feedback at: < xerces-c-dev@xml.apache.org > Can I use Xerces in my product?Yes! Read the license agreement first and if you still have further questions, then please address them to <xerces-c-dev@xml.apache.org > . Copyright © 2000 The Apache Software Foundation. All Rights Reserved. |
||||||||||||||||
|
With any suggestions or questions please feel free to contact us | ||||||||||||||||||