Re: [PATCH] convert: mark a file-local symbol static

From: Ramsay Jones <ramsay@ramsayjones.plus.com>
Date: Oct 17, 2016, 17:21 UTC
Message-ID: <16298e68-c0f9-b7ff-d4b5-0d4b79306377@ramsayjones.plus.com>
In-Reply-To: <20161017093754.wah5d6cg4qgtw7ln@sigill.intra.peff.net>

On 17/10/16 10:37, Jeff King wrote:

Show 23 quoted lines

> On Mon, Oct 17, 2016 at 11:04:19AM +0200, Johannes Schindelin wrote:
> 
>>> Gross. I would not be opposed to a Makefile rule that outputs the
>>> correct set of OBJECTS so this (or other) scripts could build on it.
>>
>> You could also use the method I use in Git for Windows to "extend" the
>> Makefile:
>>
>> -- snipsnap --
>> cat >dummy.mak <<EOF
>> include Makefile
>>
>> blub: $(OBJECTS)
>> 	do-something-with $^
>> EOF
>>
>> make -f dummy.mak blub
> 
> Hacky but clever. I like it.
> 
> In the particular case of git, I think I've cheated similarly before by
> putting things in config.mak, though of course an arbitrary script can't
> assume it can overwrite that file.

Heh, I actually have the following in my config.mak already:

extra-clean: clean
	find . -iname '*.o' -exec rm {} \;

But for some reason I _always_ type 'make clean' and then, to top it off, I _always_ type the 'find' command by hand (I have no idea why) :-D

ATB, Ramsay Jones