dynamic include in Makefile.am

2010-04-02 Thread Tim Just
Hi, the project I am working on uses GNU autotools as build system and has the following structure: app/ lib/ modules/ configure.ac Makefile.am We use one central Makefile.am to avoid the recursive use of make. This central Makefile.am contains all information related to app/ and lib/. However e

Re: dynamic include in Makefile.am

2010-04-02 Thread Ralf Wildenhues
Hello Tim, * Tim Just wrote on Fri, Apr 02, 2010 at 10:04:13AM CEST: > We use one central Makefile.am to avoid the recursive use of make. This > central Makefile.am contains all information related to app/ and lib/. > However each module defines its build system information in an own > Makefile.am

Re: revision control info in generated files

2010-04-02 Thread Jef Driesen
On 01/04/10 20:31, Ralf Wildenhues wrote: * Jef Driesen wrote on Thu, Apr 01, 2010 at 02:34:29PM CEST: On 31/03/10 22:45, Ralf Wildenhues wrote: * Jef Driesen wrote on Wed, Mar 31, 2010 at 02:49:48PM CEST: Shouldn't the .git-version file be created inside the build directory, rather than the s

Re: dynamic include in Makefile.am

2010-04-02 Thread Tim Just
Hello Ralf, thanks for your reply! On 04/02/2010 11:45 AM, Ralf Wildenhues wrote: > Hello Tim, > > * Tim Just wrote on Fri, Apr 02, 2010 at 10:04:13AM CEST: >> We use one central Makefile.am to avoid the recursive use of make. This >> central Makefile.am contains all information related to app/

Re: revision control info in generated files

2010-04-02 Thread Ralf Wildenhues
* Jef Driesen wrote on Fri, Apr 02, 2010 at 11:45:20AM CEST: > On 01/04/10 20:31, Ralf Wildenhues wrote: > >* Jef Driesen wrote on Thu, Apr 01, 2010 at 02:34:29PM CEST: > >>Since the .git-version file is a generated file, I would think it > >>belongs in the build directory, where all other generate

Re: dynamic include in Makefile.am

2010-04-02 Thread Ralf Wildenhues
* Tim Just wrote on Fri, Apr 02, 2010 at 12:07:08PM CEST: > The automake include works are functioning for me. The only drawback is > the requirement to have automake installed in order to build the project > - but that is ok :) automake should not be required at build time, except for ... > We w

Re: revision control info in generated files

2010-04-02 Thread Jef Driesen
On 02/04/10 11:58, Ralf Wildenhues wrote: * Jef Driesen wrote on Fri, Apr 02, 2010 at 11:45:20AM CEST: On 01/04/10 20:31, Ralf Wildenhues wrote: * Jef Driesen wrote on Thu, Apr 01, 2010 at 02:34:29PM CEST: Since the .git-version file is a generated file, I would think it belongs in the build d

Re: revision control info in generated files

2010-04-02 Thread Peter Johansson
On 4/2/10 7:04 AM, Jef Driesen wrote: The problem I'm trying to solve is that I already have a version.h that is generated from a version.h.in template that contains: #define MYLIB_VERSION_MAJOR @MYLIB_VERSION_MAJOR@ #define MYLIB_VERSION_MINOR @MYLIB_VERSION_MINOR@ #define MYLIB_VERSION_MICR

question about having documentation output NOT be cleaned...

2010-04-02 Thread Ed Hartnett
Howdy all! I am maintaining a free software package called netCDF, which provided array-oriented data access for Earth scientists. I use automake to build netcdf. But one little problem is in the documentation directory. Most of our documentation come from .texi files, but we all have some man pa