($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCHv2] glib-testing: add recipe
Date: Mon, 13 May 2024 02:05:01 +0200	[thread overview]
Message-ID: <20240513000501.1150851-1-f_l_k@t-online.de> (raw)

glib-testing is a build dependency for malcontent, where building the tests cant be disabled.
We can only disable the run of installed tests in malcontent.

Normally glib-testing gets included as a subproject wrap which is inappropriate for
yocto/oe. Thus we need to provide a recipe for it.

Signed-off-by: Markus Volk <f_l_k@t-online.de>
---
 .../recipes-core/glib-2.0/glib-testing_0.1.1.bb    | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 meta-oe/recipes-core/glib-2.0/glib-testing_0.1.1.bb

diff --git a/meta-oe/recipes-core/glib-2.0/glib-testing_0.1.1.bb b/meta-oe/recipes-core/glib-2.0/glib-testing_0.1.1.bb
new file mode 100644
index 000000000..ebcc2b267
--- /dev/null
+++ b/meta-oe/recipes-core/glib-2.0/glib-testing_0.1.1.bb
@@ -0,0 +1,14 @@
+SUMMARY = "libglib-testing provides test harnesses and mock classes to complement GLib classes"
+HOMEPAGE = "https://gitlab.gnome.org/pwithnall/libglib-testing"
+LICENSE = "LGPL-2.1-only"
+LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
+
+SRC_URI = "git://gitlab.gnome.org/pwithnall/libglib-testing.git;protocol=https;branch=main"
+
+PV = "0.1.1"
+S = "${WORKDIR}/git"
+SRCREV = "e326f73a7139c5e54fcf926896ae6e4cc899a1a7"
+
+inherit  meson pkgconfig
+
+DEPENDS = "glib-2.0 gtk-doc-native libxslt-native docbook-xsl-stylesheets-native python3-pygments-native"
-- 
2.44.0



                 reply	other threads:[~2024-05-13  0:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240513000501.1150851-1-f_l_k@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).