I only need icu for format-string and collation. For what it's worth: I am building for/on AMD 64 bit machine using Visual Studio 2005 (v8). Checked out a copy of the Xalan trunk a week ago. I could get neither ICU 3.2.1, 3.4, nor 3.6 to build. ICU 3.8 built and then XalanICU.sln would build properly. ICU 4.0 built, but XalanICU.sln was unable to build properly as a deprecated&apparently_removed genrb command line argument was being used.
Robert Goffena Ball Aerospace & Technologies Corp. 2875 Presidential Dr. Fairborn, OH 45324-6269 Phone: (937) 320-4096 Fax: (937) 429-1687 Email: rgoff...@ball.com -----Original Message----- From: David Bertoni [mailto:dbert...@apache.org] Sent: Thursday, April 30, 2009 4:29 PM To: xalan-c-users@xml.apache.org Subject: Re: What Version Of ICU Does Trunk Use Goffena, Robert wrote: > What version of ICU is the trunk capable of using? > > http://svn.apache.org/repos/asf/xalan/c/trunk If you plan to use the ICU message loader, as well as for the number-format function and collation, you need 3.2.1 or earlier. If you just want to use ICU integration for the number-format function and for collation, you can use any version. For Windows: To use the ICU for the former, use the XalanICU solution. To use the ICU for the latter, use the Xalan solution, and choose one of the "with ICU" configurations. For the runConfigure platforms: Export XALAN_USE_ICU in your shell, and choose either the "inmem", "icu", or "nls" message loader, using the "-m" option. I recommend you use the "inmem" option, unless you really plan to localize all of the error messages. At some point, I will try to update the build scripts so we can support message loading with newer versions of the ICU, but it's not a high priority. Dave This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address.
