expat commit access

[Greg Stein <gs...@lyra.org>]

fyi, I just received access to commit changes to Expat proper. That should
mean that we won't need to maintain any local changes in APRUTIL's copy of
expat.
[ and if we want, we can just tell people to always use expat cvs directly,
  much like we pull in httpd-2.0, apr, and apr-util into an Apache tree ]

There are definitely some local changes at the moment, but I'll be sending
all that back RSN.

I also get the impression the existing Windows build is sketchy at best.
Having OtherBill give it a good shakedown will help tremendously.

When apr-util/xml/expat builds properly under Windows, then we can toss the
old expat-lite.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: expat commit access

[Sam TH <sa...@uchicago.edu>]

On Thu, Mar 01, 2001 at 06:46:03AM -0800, Greg Stein wrote:
> I also get the impression the existing Windows build is sketchy at best.
> Having OtherBill give it a good shakedown will help tremendously.
> 
> When apr-util/xml/expat builds properly under Windows, then we can toss the
> old expat-lite.

Using unix-style tools (via cygwin) but with VC++, that expat source
builds under windows (modulo the patches I have already sent) about
once an hour, on the AbiWord tinderbox host.  So it does compile
properly.  The only question is the integration with the VC++ build
system. 
           
	sam th		     
	sam@uchicago.edu
	http://www.abisource.com/~sam/
	GnuPG Key:  
	http://www.abisource.com/~sam/key