You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-users@xalan.apache.org by David Hubbard <DH...@opentext.com> on 2008/02/27 17:08:14 UTC
building xalan-c with vs 2005
Hi everyone,
I have been trying to build xalan-c 1.10 and have failed miserably. I
have seen the previous messages on the problem and know the latest svn
fixes the problem. So I will try to follow this approach, but I cannot
use the latest if it does not have release status. So I wanted to ask
the questions that Hans Smit asked in a post on
September 24, 2007:
1) When is the latest SVN going to be promoted to release?
2) What is/will it's version number be?
3) what version of Xerces is required? 2.8?
4) Are there any release notes available that outline the changes made
since v1.10.0?
Any help you could provide would be appreciated.
David Hubbard
RE: building xalan-c with vs 2005
Posted by David Hubbard <DH...@opentext.com>.
Thanks Dave. I will follow up later.
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, February 27, 2008 1:47 PM
To: xalan-c-users@xml.apache.org
Subject: Re: building xalan-c with vs 2005
David Hubbard wrote:
> Thanks Dave.
> I have read a little about the test suite for xalanc. If I build with
> the latest from svn
> can I run it against the test suite to test stability?
Yes, you can check out the test project from the repository:
svn co https://svn.apache.org/repos/asf/xalan/test/trunk test
You can then build and run the conf project. Run it like this:
conf \xalandir\test\tests\conf -out Cresults
There will be failures depending on whether or not you build with the
ICU,
and what sorts of code page converters you have installed on your
system.
There are also some tests that are incorrect, but have not been fixed,
because Xalan-J has some bugs, and I've been unable to get the Xalan-J
team
to agree to fix them.
There are also some expected failures due to limitations in the
implementations. If you're interested, you can post your failures, and
I
can help figure out if they're expected or not.
Dave
Re: building xalan-c with vs 2005
Posted by David Bertoni <db...@apache.org>.
David Hubbard wrote:
> Thanks Dave.
> I have read a little about the test suite for xalanc. If I build with
> the latest from svn
> can I run it against the test suite to test stability?
Yes, you can check out the test project from the repository:
svn co https://svn.apache.org/repos/asf/xalan/test/trunk test
You can then build and run the conf project. Run it like this:
conf \xalandir\test\tests\conf -out Cresults
There will be failures depending on whether or not you build with the ICU,
and what sorts of code page converters you have installed on your system.
There are also some tests that are incorrect, but have not been fixed,
because Xalan-J has some bugs, and I've been unable to get the Xalan-J team
to agree to fix them.
There are also some expected failures due to limitations in the
implementations. If you're interested, you can post your failures, and I
can help figure out if they're expected or not.
Dave
RE: building xalan-c with vs 2005
Posted by David Hubbard <DH...@opentext.com>.
Thanks Dave.
I have read a little about the test suite for xalanc. If I build with
the latest from svn
can I run it against the test suite to test stability?
-----Original Message-----
From: David Bertoni [mailto:dbertoni@apache.org]
Sent: Wednesday, February 27, 2008 12:19 PM
To: xalan-c-users@xml.apache.org
Subject: Re: building xalan-c with vs 2005
David Hubbard wrote:
> Hi everyone,
>
> I have been trying to build xalan-c 1.10 and have failed miserably. I
> have seen the previous messages on the problem and know the latest svn
> fixes the problem. So I will try to follow this approach, but I cannot
> use the latest if it does not have release status. So I wanted to ask
> the questions that Hans Smit asked in a post on
> September 24, 2007:
I'm curious as to why you think having "release status" confers any
benefit. The current SVN is more stable and bug-free than the 1.10
release. Also, I'll be checking in project files for VS2008, along with
64-bit build configurations, and some tweaks to allow building 64-bit
Windows binaries.
>
> 1) When is the latest SVN going to be promoted to release?
I have no idea. There are a number of patches that need to be
integrated,
and committers' time is very limited right now.
>
> 2) What is/will it's version number be?
I would imagine 1.11
>
> 3) what version of Xerces is required? 2.8?
We've a pretty good history of maintaining compatibility with earlier
Xerces-C releases. I would imagine you could use 2.6 and 2.7, if not
earlier versions.
>
> 4) Are there any release notes available that outline the changes made
> since v1.10.0?
Your best bet is to look at the Jira issues closed since the last
release,
as all commits (except minor tweaks) will have a corresponding issue.
Dave
Re: building xalan-c with vs 2005
Posted by David Bertoni <db...@apache.org>.
David Hubbard wrote:
> Hi everyone,
>
> I have been trying to build xalan-c 1.10 and have failed miserably. I
> have seen the previous messages on the problem and know the latest svn
> fixes the problem. So I will try to follow this approach, but I cannot
> use the latest if it does not have release status. So I wanted to ask
> the questions that Hans Smit asked in a post on
> September 24, 2007:
I'm curious as to why you think having "release status" confers any
benefit. The current SVN is more stable and bug-free than the 1.10
release. Also, I'll be checking in project files for VS2008, along with
64-bit build configurations, and some tweaks to allow building 64-bit
Windows binaries.
>
> 1) When is the latest SVN going to be promoted to release?
I have no idea. There are a number of patches that need to be integrated,
and committers' time is very limited right now.
>
> 2) What is/will it's version number be?
I would imagine 1.11
>
> 3) what version of Xerces is required? 2.8?
We've a pretty good history of maintaining compatibility with earlier
Xerces-C releases. I would imagine you could use 2.6 and 2.7, if not
earlier versions.
>
> 4) Are there any release notes available that outline the changes made
> since v1.10.0?
Your best bet is to look at the Jira issues closed since the last release,
as all commits (except minor tweaks) will have a corresponding issue.
Dave