I am writing with a question that all of my associates have faced when trying to use xerces together with xalan.  Why aren't the source trees more closely related?  It takes hours of time and a lot of energy to get Xalan to compile and link.  After two days of focusing on it I finally called it a day.  It was quite a shock to learn I spent the first day wasting my time trying to link xalan with the current version of xerces which I've had on my development system for several days.
 
Not to be all negative I was quite pleased with how easily it set up on my windows workstation.  Why haven't you used automake and autoconf to their fullest?  I've installed a lot of applications on our Sun E450 with almost no problems.
 
I also think that Xalan and Xerces are the best tools available in the open source market.  I found the api easy to use and very functional.  Unfortunately, because of the difficulty in setting up Xalan, I'm going to have to find another tool because my company has 3 Dec-Alphas and 4 Solaris systems with a variety of configurations.  I can't spend 2-3 days on each machine trying to set up a third party library.  It's ridiculous.
 
If there is any way I can help other than complaining, please let me know.  I would be happy to offer some of my time to help with creating a more robust package.  I am an experienced C, C++, Java programmer with 4years of Computer Science under my belt and 6 years of industry experience working for various internet/publishing companies.

Cliff Kilpatrick, Software Engineer

Cambridge Scientific Abstracts
7200 Wisconsin Ave, Suite 600
Bethesda, MD, 20814

ph: 301.961.6787
em: [EMAIL PROTECTED]

 

Reply via email to