On Thu, Jun 13, 2013 at 9:55 PM, wrote:
> On Mon, May 27, 2013 at 01:10:58PM -0400, wrote:
>> On 05/27/13 at 10:46:11 -0400 gmn wrote:
>> > In my opinion, whatever scripts in MacVim that control this ought to
>> > be changed so that the result matches BramVim, and config.cache
>> > files will go in src/auto rather than just src. That way, "make
>> > distclean" in a MacVim repo will in fact clean them.
>>
>> That is to say, *if* it is easy to do so, then the relevant scripts
>> ought to be changed so that blah blah.
>>
>> (Or perhaps 'make distclean' can be patched to also obliterate any
>> existing src/config.cache)
>>
>> If it isn't an easy thing, just forget it. I can deal with it.
>
> Hi Björn,
>
> Although I discovered how to trigger the issue, I don't know what causes
> it. I don't know enough about makefiles or confiure scripts to wade
> through the difference between those of MacVim and those of BramVim. So
> I propose modifying, in MacVim, src/Makefile according the the below
> diff.
>
> The line two lines above my added one is doing almost nothing at all,
> because the files auto/config.{status,log,cache} are never created by
> MacVim as far as I can see:
>
> ** If I call './configure -C', they get put in src/, which is what
> generated this bug-reporting thread.
>
> ** If on the other hand I call plain './configure', then no caches are
> created, so there's nothing for that line of the Makefile to destroy.
>
> ** If I call './configure --cache-file=src/auto/config.cache (which
> './configure --help tells me is kosher), then no config.cache is put
> *anywhere*, and config.{log,status} are put straight into src/ where
> the latter won't get wiped out by 'make distclean'.
>
> Therefore I propose leaving that line in place (since it's doing no
> harm), but adding one that allows 'make distclean' to destroy
> 'src/config.{cache,log,status}'. I tested this locally and it seems to
> work. Thus 'make distclean' will destroy the things it's supposed to
> destroy.
I think it would be better to figure out why there is a difference
instead of blindly patching. I don't know what causes it though, so I
can't help.
Björn
--
--
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_mac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_mac+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
