From: <colin.helliwell@ln-systems.com>
To: <yocto@yoctoproject.org>
Subject: DEPENDS only half working
Date: Wed, 1 Feb 2017 10:38:51 -0000 [thread overview]
Message-ID: <04fb01d27c77$613d3780$23b7a680$@ln-systems.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
I've got an odd problem with a pair of recipes:
App 'bar' uses 'libfoo', so I've set a DEPENDS in bar.bb - I can see this is
being half picked up, because 'bitbake bar' shows both builds being started.
However bar isn't waiting on libfoo - bar tries to compile before libfoo has
even finished configuring, let alone compiled and installed it's header
(foo_lib.h) into sysroot.
I think the recipes are probably otherwise correct - if I 'bitbake libfoo'
then 'bitbake bar' then all works.
I've looked at some simple lib recipes within poky (e.g. libwebp_0.4.3.bb /
webkitgtk_2.8.5.bb), and can't spot anything wrong/missing. Not sure if
libfoo should have any 'install' or similar sections, or any FILES_
settings, but I was [naively.?] hoping that the inherited classes will be
sorting out all that generic kinda stuff.
Anyone help please?
libfoo.bb :
.
inherit autotools lib_package binconfig-disabled pkgconfig
RPROVIDES_${PN} = "libfoo"
PROVIDES_${PN} = "libfoo"
PR = "r0"
SRC_URI = " ...<src files>.. "
S = "${WORKDIR}"
bar.bb :
..
inherit autotools binconfig-disabled pkgconfig
DEPENDS_${PN} = "libfoo"
RDEPENDS_${PN} = "libfoo"
S = "${WORKDIR}"
SRC_URI = " ...<src files>.. "
EXTRA_OEMAKE = " CFLAGS=" -I${STAGING_DIR_TARGET}/usr/include/libfoo " "
EXTRA_OEMAKE += " LDFLAGS=" -lfoo " "
libfoo Makefile.am:
lib_LTLIBRARIES = libfoo.la
pkginclude_HEADERS = foo_lib.h
libfoo_la_SOURCES = $(libfoo_a_HEADERS) foo_lib.c
[-- Attachment #2: Type: text/html, Size: 4632 bytes --]
next reply other threads:[~2017-02-01 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 10:38 colin.helliwell [this message]
2017-02-01 10:48 ` DEPENDS only half working Patrick Ohly
2017-02-01 10:53 ` colin.helliwell
2017-02-01 12:52 ` Jussi Kukkonen
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='04fb01d27c77$613d3780$23b7a680$@ln-systems.com' \
--to=colin.helliwell@ln-systems.com \
--cc=yocto@yoctoproject.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.