[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Make feature request, pattern matching
From: |
Noah Slater |
Subject: |
Re: GNU Make feature request, pattern matching |
Date: |
Wed, 1 Oct 2008 15:41:24 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Oct 01, 2008 at 03:28:43PM +0100, Dave Korn wrote:
> Using a different extension for the processed and unprocessed files would
> resolve this. Compare, e.g. the way gcc uses ".c" to mean a C source file and
> ".i" to mean the same file after pre-processing.
Yes, I have been tossing this idea around but I don't like it because it adds an
additional layer of complexity to the software configuration.
> > I am generating the targets dynamically (by scanning the source directory
> > using Python and using GNU Make's standard makefile generation hooks)
>
> Googlewhacked! You are the only person on the entire internet in the whole
> of history to have used the phrase "makefile generation hooks"! Could you
> clarify what you're referring to, using the same terminology that the manual
> uses to describe whatever-it-is you're talking about?
See the information in the following section:
3.7 How Makefiles Are Remade
Thanks,
--
Noah Slater, http://bytesexual.org/nslater