<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Mon, 2010-09-20 at 00:39 -0400, Trevor Woerner wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">The build wiki page on the fd.o site talks about building from</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">tarballs but suggests using the "build-from-tarballs.sh" script</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">instead of the "build.sh" script. Is the checkfortars() function code</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">that is being used in some way, or is it a left-over from something</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">else?</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
I know that, generally speaking, people build from tarballs, but I am not aware if they do so<BR>
from build.sh. The build-from-tarballs script hasn't seen its module list updated in 2 years.<BR>
As hinted recently, this is duplication of modules list.<BR>
<BR>
When building from a tarball, I suppose, but I am not sure, that it is mostly for<BR>
obtaining a previous version, or the latest published version as opposed to git master.<BR>
There is no need to recreate the configuration, just running ./configure and make install.<BR>
<BR>
Note that autogen.sh is not part of the GNU packaging architecture and is not shipped in tarballs.<BR>
If it helps, you can ignore that file and invoke "autoreconf -vfi" followed by<BR>
./configure --enable-maintainer-mode. <BR>
<BR>
You can find some background info on module configuration you can expect to be there as<BR>
a result of project policy: <A HREF="http://wiki.x.org/wiki/NewModuleGuidelines">http://wiki.x.org/wiki/NewModuleGuidelines</A><BR>
<BR>
To find out if the directory contains a fresh clone, you can check for the presence of some files<BR>
generated by autoreconf. You can rely on Makefile.am to be present in all xorg modules root dir.<BR>
<BR>
It will help to inventory the files created as a result of run autoreconf vs ./configure. Keep in mind<BR>
that the tarball generally gets created on one platform (say GNU/Linux) and gets configured and built<BR>
on another (say Solaris). The developer scenario from git blurs the distinction between these steps.<BR>
<BR>
Gaetan<BR>
<BR>
</BODY>
</HTML>