From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: provide a script for checking glib symbol usage
Date: Fri, 18 Dec 2015 13:35:13 +0000 [thread overview]
Message-ID: <20151218133513.GD2459@work-vm> (raw)
In-Reply-To: <56740537.9010106@redhat.com>
* Paolo Bonzini (pbonzini@redhat.com) wrote:
>
>
> On 18/12/2015 14:05, Daniel P. Berrange wrote:
> > > > +
> > > > +cs-glib-syms:
> > > > + @perl scripts/glib-syms.pl $(GLIB_SYMS_LIST) $(C_CODE_FILES)
> > >
> > >
> > > Does this need to be included, or could it be a separate Makefile
> > > invoked with e.g. make -f scripts/Makefile.style?
> >
> > Any particular reason to favour that over include ? I did it this
> > way because QEMU in general seems to be biased towards includes
> > and not recursive make
>
> That would not be recursive make, but rather a completely separate
> Makefile to be manually invoked with -f.
Hmm but wouldn't this Makefile also be a good place for small-fast
style check scripts that could be included in make check ?
Dave
>
> Paolo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-12-18 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:36 [Qemu-devel] [PATCH] scripts: provide a script for checking glib symbol usage Daniel P. Berrange
2015-12-18 12:36 ` Paolo Bonzini
2015-12-18 13:05 ` Daniel P. Berrange
2015-12-18 13:08 ` Paolo Bonzini
2015-12-18 13:35 ` Dr. David Alan Gilbert [this message]
2015-12-18 13:37 ` Daniel P. Berrange
2015-12-18 13:42 ` Dr. David Alan Gilbert
2015-12-18 13:49 ` Peter Maydell
2015-12-18 13:52 ` Dr. David Alan Gilbert
2015-12-18 13:41 ` Paolo Bonzini
2015-12-18 13:43 ` Peter Maydell
2015-12-18 14:49 ` Daniel P. Berrange
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=20151218133513.GD2459@work-vm \
--to=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).