qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michal Privoznik <mprivozn@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Makefile: Properly order build targets 'all' and 'check'
Date: Tue, 23 Jun 2015 15:35:31 +0200	[thread overview]
Message-ID: <558960A3.5010509@redhat.com> (raw)
In-Reply-To: <20150623144917.372248b1@thh440s>

On 23.06.2015 14:49, Thomas Huth wrote:
> On Tue, 23 Jun 2015 14:42:35 +0200
> Michal Privoznik <mprivozn@redhat.com> wrote:
> 
>> On 23.06.2015 14:37, Peter Maydell wrote:
>>> On 23 June 2015 at 13:30, Michal Privoznik <mprivozn@redhat.com> wrote:
>>>> I'm used to run 'make -j5 all check'. However, this is not possible in
>>>> qemu because of the missing dependency in the Makefile. If I do that,
>>>> tests are usually started with build and since not everything is built
>>>> yet, they often fail too. Moreover, we should run test suite only
>>>> after every binary we want to test has been built.
>>>>
>>>> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>>>> ---
>>>>  Makefile | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Makefile b/Makefile
>>>> index e7c5c3a..67eeb87 100644
>>>> --- a/Makefile
>>>> +++ b/Makefile
>>>> @@ -151,6 +151,7 @@ dummy := $(call unnest-vars,, \
>>>>
>>>>  ifneq ($(wildcard config-host.mak),)
>>>>  include $(SRC_PATH)/tests/Makefile
>>>> +check: all
>>>>  endif
>>>>  ifeq ($(CONFIG_SMARTCARD_NSS),y)
>>>>  include $(SRC_PATH)/libcacard/Makefile
>>>
>>> I'm having difficulty understanding the use of conditionals
>>> in our makefile -- can you explain why inside this ifneq
>>> rather than outside is the right place for this dependency?
>>
>> Well, I guess it could be outside too. My thinking was, that we include
>> the tests/Makefile - which defines the 'check' target - only
>> conditionally, therefore the dependency should be defined only sometimes
>> too. I guess it won't hurt if it was outside too.
> 
> Maybe it's simpler to add the dependency into tests/Makefile instead?
> 

Yeah, that could work too. For some reason I thought that having it
there would result in making 'all' just under tests/. But Now that I
tried it out it works just nicely. Do you want me to post v2 or is that
something that can be fixed just before pushing?

Michal

  reply	other threads:[~2015-06-23 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 12:30 [Qemu-devel] [PATCH] Makefile: Properly order build targets 'all' and 'check' Michal Privoznik
2015-06-23 12:37 ` Peter Maydell
2015-06-23 12:42   ` Michal Privoznik
2015-06-23 12:49     ` Thomas Huth
2015-06-23 13:35       ` Michal Privoznik [this message]
2015-06-23 17:29         ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2015-06-23 17:31         ` [Qemu-devel] " Peter Maydell
2015-06-23 17:46           ` Stefan Weil
2015-06-25  7:08             ` Markus Armbruster
2015-06-25  9:13               ` Michal Privoznik

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=558960A3.5010509@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@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;
as well as URLs for NNTP newsgroup(s).