[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Putting intermediate files in the distribution?

From: Paul Brook
Subject: Re: Putting intermediate files in the distribution?
Date: Wed, 2 Apr 2003 19:06:38 +0100
User-agent: KMail/1.5

On Wednesday 02 April 2003 10:06 am, Bob Proulx wrote:
> I am autoconfiscating a moderately large legacy project.  A previously
> existing methodology in the project is to create a large number of .c
> and .h files by generating them with a script from a template.  I have
> created custom rules to do this and all builds fine.  I originally put
> the generated files into CLEANFILES since they are generated files.
> But upon a clean build I notice that it takes longer to run the
> scripts to build those .c and .h files than it takes to compile the
> entire rest of the project!  Yes the scripts are slow and I can
> probably speed them up.  But for now I just want to work around the
> problem and put that task off until later.  The files are architecture
> independent and produce identical files on any platform.  Therefore I
> would like to include those into the distribution in order to save the
> rebuild time every time I recompile from scratch.
> I have been thinking I should put the generated .c and .h files into
> both EXTRA_DIST and MAINTAINERCLEANFILES.  Then I could force a
> rebuild of those with maintainer-clean when I really want to force
> rebuild them.  They would get normal dependency management and be
> rebuilt when needed based upon their dependencies changing.  But they
> would avoid being rebuilt gratuitously.  I have tested this and it
> seems to do what I want but seems questionable to me.  I was looking
> for direction.  Does this scheme sound right?

Putting the files into BUILT_SOURCES should do what you want. This includes 
them in the distribution, and removes them when you do "make 

Paul Brook

reply via email to

[Prev in Thread] Current Thread [Next in Thread]