From: Michael Snyder <msnyder@vmware.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfa] make clean should remove observe.h and observer.inc
Date: Thu, 24 Feb 2011 18:25:00 -0000 [thread overview]
Message-ID: <4D669D92.2090005@vmware.com> (raw)
In-Reply-To: <m3bp21h5js.fsf@fleche.redhat.com>
Tom Tromey wrote:
> Michael> 2011-02-23 Michael Snyder <msnyder@vmware.com>
> Michael> * Makefile.in (clean): Make clean should remove generated files
> Michael> observer.h and observer.inc.
>
> I think this is ok.
I'll check it in, then,
> There is a sort of GNU rule governing "clean" behavior. I'm not sure
> whether this is documented in the GNU standards but it is longstanding
> practice, existing before and then codified in Automake:
>
> * 'mostlyclean' is a "useful" subset of 'clean'
> * If 'make' built it, 'clean' removes it
> * If 'configure' built it, 'distclean' removes it
> * If the developer built it, but it is a generated file not needed for
> "configure; make", then `maintainer-clean' removes it.
>
> I looked a little more and I found this in the Automake manual's "Clean"
> node.
That brings up another question. What about <lang>-exp.c? Technically
they are generated files. Should make clean remove them?
next prev parent reply other threads:[~2011-02-24 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:56 Michael Snyder
2011-02-23 21:44 ` Michael Snyder
2011-02-24 7:20 ` Jan Kratochvil
2011-02-24 15:46 ` Tom Tromey
2011-02-24 18:25 ` Michael Snyder [this message]
2011-02-24 18:27 ` Joel Brobecker
2011-02-24 18:39 ` Michael Snyder
2011-02-24 18:57 ` Tom Tromey
2011-02-24 19:04 ` Mark Kettenis
2011-02-24 19:01 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D669D92.2090005@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox