From: Markus Volk <f_l_k@t-online.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-gnome][PATCH] folks: make some dependencies optional
Date: Fri, 28 Jan 2022 18:35:16 +0100 [thread overview]
Message-ID: <81dde554-b80e-43aa-cc85-033f858ff2a0@t-online.de> (raw)
In-Reply-To: <26359.1643390123448861343@lists.openembedded.org>
https://github.com/openembedded/meta-openembedded/blob/aa22894fa352986a62c4530ad8facd8868b2e535/meta-gnome/recipes-connectivity/folks/folks_0.15.4.bb#L24
Doesn't this line explicitly disable tests until DISTRO_FEATURE ptests
is set ?
Am 28.01.22 um 18:15 schrieb Ross Burton:
> +PACKAGECONFIG[tests] = "-Dtests=true,-Dtests=false,python3-dbusmock-native"
>
> You don't install the tests, so this serves no purpose.
>
> Just set -Dtests=false explicitly, unless you install the tests and do the ptest integration.
>
> Also the dbusmock test in folks is broken, it should be cross-aware. As you can't check for target python modules it should avoid the check in cross builds.
>
> Ross
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#95149): https://lists.openembedded.org/g/openembedded-devel/message/95149
> Mute This Topic: https://lists.openembedded.org/mt/88678231/3618223
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [f_l_k@t-online.de]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2022-01-28 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 18:13 [meta-gnome][PATCH] folks: make some dependencies optional Markus Volk
2022-01-28 17:15 ` Ross Burton
2022-01-28 17:33 ` [oe] " Khem Raj
2022-01-28 17:35 ` Markus Volk [this message]
2022-01-28 17:38 ` Khem Raj
2022-01-28 17:42 ` Markus Volk
2022-01-28 17:43 ` Khem Raj
2022-01-28 17:54 ` Markus Volk
2022-01-28 18:28 ` Khem Raj
2022-01-29 14:21 ` Markus Volk
2022-01-28 17:43 ` Ross Burton
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=81dde554-b80e-43aa-cc85-033f858ff2a0@t-online.de \
--to=f_l_k@t-online.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.