Re: Makefile.in's in build tree

[John Calcote]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kamaljit Singh wrote:
> Hi,
> 
>   I maintain my build tree separate to src tree which has all the 
> Makefile.am's.
> Is it possible that all generated files (including the Makefile.in's and the 
> various cache) be in the build tree ?
> 
> kamaljit
> 

There are three levels of files here:

1. Level 1 includes files that are generally checked into the source
repository. These are handed edited by the developers. They usually
can't be built any other way.

2. Level 2 includes build system files that are generated or installed
by the autotools. These are also part of the source tree, but not
necessarily part of the final application. They have to stay in the
source tree, because they get packaged up with distribution tarballs.

3. Level 3 includes build products, such as Makefiles, object files,
libraries, programs, etc. These files are built by the user from Level 1
and 2 files shipped in distribution tarballs.

Makefile.in files, configure scripts, auxiliary shell scripts, etc are
autotools-generated or installed build files that are shipped in
distribution tarballs, so they are part of the level 2 file set. As
such, they must remain in the source tree. In fact, they appear to be
part of the source tree to end users who unpack tarballs and find them
there.

Regards,
John

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD4DBQFIUpUrdcgqmRY/OH8RAoBlAJMHhr9s9WYL9yCLOYkEhLuNq11YAJ0ZethX
JooRaauYTqbk2E8s6Fmp/Q==
=uj34
-----END PGP SIGNATURE-----