[fdo-internals] Remove Generated Files

Mateusz Loskot mateusz at loskot.net
Mon Oct 29 16:55:43 EDT 2007

Ah, and one more note.

The autogen.sh script I explained previously, just calls these tools
as build_linux.sh does. Simply, build_linux.sh == autogen.sh.

-- Mat

Greg Boone wrote:
> Actually, I would state that it is no more work (at least initially)
> since we recommend users call build_linux.sh, which calls
>       aclocal
>       libtoolize --force
>       automake --add-missing --copy
>       autoconf
>      ./configure
> This generates the makefiles. Once this is done, the user is free to
> call 'make' and 'make install' directly.
> Greg
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz
> Loskot
> Sent: Monday, October 29, 2007 4:47 PM
> To: FDO Internals Mail List
> Subject: Re: [fdo-internals] Remove Generated Files
> Jason Birch wrote:
>> It would be nice if the trunk could remain as accessible as possible
> to
>> non-developers.  I don't know what kind of effort there is using
>> autotools, but just wanted to get a word in.
> In many projects, especially in GNU world, ./configure is forbidden in
> CVS/SVN as a dynamic content.
> So, there is a special script provided that generates it for you.
> For example, in GDAL ./configure lives in the repository,
> but there is also autogen.sh script which can be used to generate
> configure. Let's assume there is no ./configure in FDO repo, then
> if you want to build SVN version, you have to run:
> ./autogen
> ./configure
> make
> make install
> So, it's just one step more.
> Cheers

Mateusz Loskot

More information about the fdo-internals mailing list