Subject: Re: documentation for in-tree autoconf & wrapper
To: Blair Sadewitz <email@example.com>
From: Michael Lorenz <firstname.lastname@example.org>
Date: 01/08/2007 15:35:12
-----BEGIN PGP SIGNED MESSAGE-----
On Jan 8, 2007, at 15:17, Blair Sadewitz wrote:
> I think I may just be burnt-out after working with all of those
> packages in modular Xorg too often. ;)
I do understand that all too well...
> What Christos suggests is what I was planning on trying.
Unlike me Christos should know what he's talking about here ;)
> The only problem I see--and again, I could be seeing ghosts here--is
> that in
> modular Xorg, they don't use autoconf to simply produce things like
> config.h. If that were the case, I wouldn't worry much.
> Unfortunately, their methodology is more complex than that.
Usually - as far as I can tell - it boils down to include or exclude
some files based on platform and pass extra flags to some files.
> Moreover, unlike XFree86, there are many dependencies involving
> important headers which all must be installed prior to building any
> module which requires them. Thus, if we were to simply use autoconf,
> we'd need a shadow root, right?
This looks like something that can be done before building.
> Given the percentage of our supported platforms which will ever
> likely have DRI, though, we could either have the users build the
> drivers themselves or distribute them in binary form built somewhere
> else other than the
> autobuild cluster.
Yeah, i386, amd64, macppc, maybe sparc64 - that's pretty much it.
> Thanks for all of your input, I appreciate it.
Thanks for tackling the beast - everyone appreciates that ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----