Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [morty][PATCH] libevdev: add libcheck dependency
Date: Fri,  3 Nov 2017 13:29:20 -0700	[thread overview]
Message-ID: <1509740960-11858-1-git-send-email-armccurdy@gmail.com> (raw)

The libevdev configure script contains an unconditional check for
libcheck. If libcheck is found, libevdev unit tests will be built.

Without a dependency, the presence of libcheck in sysroot is non
deterministic (in morty and earlier) and builds can fail if libcheck
is available during do_configure but not during do_compile.

(In pyro and later, the libcheck dependency is not required to make
libevdev builds deterministic due to recipe specific sysroots).

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
 meta/recipes-support/libevdev/libevdev_1.5.2.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-support/libevdev/libevdev_1.5.2.bb b/meta/recipes-support/libevdev/libevdev_1.5.2.bb
index c76e1d7..381d252 100644
--- a/meta/recipes-support/libevdev/libevdev_1.5.2.bb
+++ b/meta/recipes-support/libevdev/libevdev_1.5.2.bb
@@ -6,6 +6,8 @@ LICENSE = "MIT-X"
 LIC_FILES_CHKSUM = "file://COPYING;md5=75aae0d38feea6fda97ca381cb9132eb \
                     file://libevdev/libevdev.h;endline=21;md5=7ff4f0b5113252c2f1a828e0bbad98d1"
 
+DEPENDS = "libcheck"
+
 SRC_URI = "http://www.freedesktop.org/software/libevdev/${BP}.tar.xz"
 
 SRC_URI[md5sum] = "96ad6edb5ce5c4428f1b183cc180ff8c"
-- 
1.9.1



             reply	other threads:[~2017-11-03 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 20:29 Andre McCurdy [this message]
2017-11-07 21:26 ` [morty][PATCH] libevdev: add libcheck dependency Andre McCurdy

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=1509740960-11858-1-git-send-email-armccurdy@gmail.com \
    --to=armccurdy@gmail.com \
    --cc=openembedded-core@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