Hi Martin, Thanks for your comments. They are helpful for planning.
The Solaris TAR issue is mentioned on the FAQ page. It does recommend using the GNU tar. The Xerces-c 3.1.1 package was released before MS .NET 2012. After the Xalan 1.11 release, I may try to upgrade both a Xerces-C patch release and Xalan-C release to accommodate Microsoft .NET 2012. The code base for Xalan-C is currently frozen. I will incorporate the Google Summer of Code 2012 work into the Xalan-C trunk after the version 1.11 official distribution. This GSoC 2012 activity will add most of the EXSLT XPath functions. The ICU stuff HAS NOT BEEN TESTED since Xerces-C parser now incorporates ICU. David Bertoni knows the old ICU interface, but he is too busy to continue the maintenance. The newest GCC that I have installed is version 4.4.5 and on a Debian Linux machine. It seems to have no problems with the libraries. Xerces-C builds OK on BSD using the native make platform. Xalan-C requires gnu make for its builds. I still have yet to hear about successful builds for OpenBSD, HPUX, and Mac OS X platforms. I am still struggling to get SunStudio 12.3 installed on my Solaris_11 virtual machines. Microsoft Visual Studio 2012 support is definitely one of my priorities. I have several vendors currently using VS 2010. I also have several vendors still using MS VS .Net 2003. I am trying to ensure that there is an upgrade path for the full Microsoft VS .NET series platforms. Sincerely, Steven J. Hathaway Xalan Documentation Project P.S. I am reworking my committer's website. It will prototype the Xalan-C 1.11 distribution in preparation for moving it to the Apache distribution mirrors. > Hi Steve, > > I've just glanced thru the following a bit. In other messages I've shared > other specifics about how USoft builds Xerces-c and Xalan on Solaris and > AIX. > it's probably handiest to compose and/or add-to pre-existing OS-specific > TODO/READ/BUILD/INSTALL/HOWTO or whatever theyàe called files (assuming > they exist) regarding such issues. > > I did have a nit and some comments about the following. > > We might want to also warn people that their 'system-default' tar > executable (assuming that that one isn't GNU tar) might have problems with > extracting longer file/path names in the documentation sections, > if so, GNU tar could work better. (I'm not sure if I had that issue with > Xalan or Xerces, but IIRC Boost definitely had such an issue on Solaris.) > > If people need to build both Xerces-c and Xalan we should warn them not to > use ICU's message loading stuff (it hasn't worked in quite a while) but > I'll need to consult my escrow notes about > the exact name of that option and such. > I think it's probably handy to encourage people not to add any ICU > dependencies to either the Xerces-c or Xalan builds unless they're certain > that they need to. > > The nit: only Visual Studio 2002 and 2003 have ".NET" in their official > names, so it can be dropped from all of the other VS version's names... > > I think we're going to have to try to build Xalan on a few more modern > versions of GCC including 4.5, 4.6 and 4.7 ... > > And one platform we also definitely have to try to build Xalan on is the > recently-released Visual Studio 2012 Desktop Express > (I feel sure if we don't then that's going to be the number-one > most frequently asked question...) > > Sincerely, > Martin > > ________________________________________ > Van: [email protected] [[email protected]] > Verzonden: woensdag 10 oktober 2012 23:27 > Aan: [email protected] > Onderwerp: Xalan-C/C++ Readme File - Request Comments > > Preparing for Xalan-C/C++ Version 1.11 Release > > The standard location for UNIX/Linux binary distribution > blurb documents is in the (prefix)/doc/<package>/ directory. > The prefix is usually /usr or /usr/local. > > I want the README file to indicate useful tips for UNIX/Linux > package integrators. > > Here are some of my thoughts... > > Sincerely, > Steven J.Hathaway > Xalan Documentation Project > > > Software Binary Distribution Documents > > ${prefix}/doc/xalan-c-1.11/ > > LICENSE > NOTICE > README > > The LICENSE file contains a text copy of the Apache License Version 2. > > The NOTICE file contains the attribution text required by License. > > The README file contains information useful for software integration. > > I am looking to provide a README file that looks like this: > ------------------------------------------------------------ > > Apache Xalan-C/C++ XSLT Library Version 1.11 > > Project Description: > The Apache Xalan C/C++ Project provides a library and a > comand line program to transform XML documents using a > stylesheet that conforms to XSLT 1.0 standards. > > The source package contains all the code to create the library, > a command line transform utility and the documentation. > > The documentation packages provide pre-built html documents > for web browser use. > > Binary prebuilt packages are available for some platforms. > We could use help providing packages for more platforms. > > Xalan is a project of the Apache Software Foundation. > > Project Website: > http://xalan.apache.org/xalan-c/ > > Subversion Repository: > http://svn.apache.org/repos/asf/xalan/c/trunk > > Mirror Download Site: > http://www.apache.org/dyn/mirrors/mirrors.cgi/xalan/xalan-c > > Prerequisite: > Apache Xerces-C/C++ XML Parser Library > Version 3.0 or newer > Version 3.1.1 preferred > > Prerequisite: > Gnu Make > This is required when building the Xalan-C library > on UNIX/Linux platforms. > > UNIX PACKAGE INSTALL PROJECTS: > > (prefix)/doc/xalan-c-1.11/ > README - This Document > LICENSE - The Software License > NOTICE - The Software Attributions > > (prefix)/bin/ > Xalan - command line XSLT stylesheet transform utility > > (prefix)/include/xalanc/ > - directory containing library header files > > (prefix)/lib/ > libxalan-c.so -> libxalan-c.so.111.0 > lib/libxalan-c.so.111 -> libxalan-c.so.111.0 > libxalan-c.so.111.0 > libxalanMsg.so -> libxalanMsg.so.111.0 > libxalanMsg.so.111 -> libxalanMsg.so.111.0 > libxalanMsg.so.111.0 > > WINDOWS PACKAGE INSTALL PRODUCTS: > > (prefix)/doc/xalan-c-1.11/ > README - This Document > LICENSE - The Software License > NOTICE - The Software Attributions > > (prefix)/bin/ > Xalan.exe - command line XSLT stylesheet transform utility > Xalan-C_1_11.dll - Release build library > Xalan-C_1_11D.dll - Debug build library > XalanMessages_1_11.dll - Release build messages > XalanMessages_1_11D.dll - Debug build messages > > (prefix)/include/xalanc/ > - directory containing library header files > > (prefix)/lib/ > Xalan-C_1.exp - Windows DLL export definitions > Xalan-C_1.lib - Windows DLL library definitions > Xalan-C_1D.exp - Windows DLL export definitions > Xalan-C_1D.lib - Windows DLL library definitions > XalanMessages_1_11.exp - Windows DLL export definitions > XalanMessages_1_11.lib - Windows DLL library definitions > XalanMessages_1_11D.exp - Windows DLL export definitions > XalanMessages_1_11D.lib - Windows DLL library defnitions > > SUPPORTED PLATFORMS: > - This is only a partial list > Linux/Gnu GCC 4.4 > Windows VC7.1 Visual Studio .NET 2003 > Windows VC8 Visual Studio .NET 2005 > Windows VC9 Visual Studio .NET 2008 > Windows VC10 Visual Studio .NET 2010 > Solaris-10 CC SunStudio 12 > OpenBSD 5.1 GCC 4.1 > FreeBSD 9 GCC 4.2 > - Known from previous releases > AIX GCC > AIX ALC > BSD GCC > HPUX ACC > Mac OS X GCC > Cygwin GCC > MinGW GCC > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally > privileged information. If you are not the intended recipient you are > hereby notified that any disclosure, copying, distribution or taking any > action in reliance on the contents of this information is strictly > prohibited and may be unlawful. If you have received this communication in > error, please notify us immediately by forwarding this email to > [email protected] and then delete it from your system. > > USoft is neither liable for the proper and complete transmission of the > information contained in this communication nor for any delay in its > receipt. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
