RE: Does Xalan care about Xerces compile settings?

[Saurabh Bhatnagar]

In a nuthshell yes, since Xalan depends on xerces source code as well as libs.

More on this tomorrow.

 

--

Saurabh Bhatnagar | Development Manager- Software config & Build Mgmt.
Phone: +18041836080 | Fax: +918041526000
Oracle Product Life cycle Services

ORACLE India | Plot #1, NR ENCLAVE, EPIP INDUSTRIAL AREA, WHITEFIELD | 560066 BANGALORE

Oracle is committed to developing practices and products that help protect the environment

 

---

From: Garyl Erickson [mailto:garyl.erick...@flec.tv]
Sent: Thursday, April 07, 2011 4:34 AM
To: xalan-c-users@xml.apache.org
Subject: Does Xalan care about Xerces compile settings?

Does Xalan care about any of the five Xerces settings that are settable during, and reported by, the configure step, which are:

    File Manager: POSIX | ...
    Mutex Manager: Windows | ...
    Transcoder: gnuiconv | iconv | icu | macosunicodeconverter | windows
    NetAccessor: curl | socket | cfurl | winsock | none
    Message Loader: inmemory | icu | iconv

I.e., does the Xalan runConfigure -t setting have to match a Xerces configure --enable-transcoder-* setting or does the Xalan runConfigure -m setting have to match a Xerces configure setting?

Also, do any of these Xerces settings have to match each other, i.e., if iconv is used for transcoder, does it also have to be used for message loader?

Thanks