Skip to contentSkip to conversation

DEPENDS only half working

DISCUSSION [email protected] 3 participants 4 messages Feb 1, 2017

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 17 lines · On Wed, 2017-02-01 at 10:38 +0000, [email protected] wrote:

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.

[...]

Quoted 1 line

DEPENDS_${PN} = "libfoo"

^^^^^^^^^^^^^
This needs to be just "DEPENDS". DEPENDS sets the dependencies for the compilation of the entire recipe, whereas...

Quoted 1 line

RDEPENDS_${PN} = "libfoo"

... RDEPENDS is for runtime dependencies specific packages and thus has _<package name> as suffix ($PN = bar in this case).

libfoo gets compiled because of this entry, but because it is a runtime dependency, compilation of bar doesn't wait for libfoo's completion.

Signature · 6 lines
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
#2 lore raw

Fantastic - thanks. (Thought it must have been something simple!)

-----Original Message-----
From: Patrick Ohly [mailto:[email protected]]
Sent: 01 February 2017 10:48
To: [email protected]
Cc: [email protected]
Subject: Re: [yocto] DEPENDS only half working

Quoted 17 lines · On Wed, 2017-02-01 at 10:38 +0000, [email protected] wrote:

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.

[...]

Quoted 1 line

DEPENDS_${PN} = "libfoo"

^^^^^^^^^^^^^
This needs to be just "DEPENDS". DEPENDS sets the dependencies for the compilation of the entire recipe, whereas...

Quoted 1 line

RDEPENDS_${PN} = "libfoo"

... RDEPENDS is for runtime dependencies specific packages and thus has _<package name> as suffix ($PN = bar in this case).

libfoo gets compiled because of this entry, but because it is a runtime dependency, compilation of bar doesn't wait for libfoo's completion.

--
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

#3 lore raw
In reply to Patrick Ohly
Quoted 22 lines · Patrick Ohly
Quoted 17 lines · On Wed, 2017-02-01 at 10:38 +0000, [email protected] wrote:

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.

[...]

Quoted 1 line

DEPENDS_${PN} = "libfoo"

Quoted 10 lines

^^^^^^^^^^^^^
This needs to be just "DEPENDS". DEPENDS sets the dependencies for the compilation of the entire recipe, whereas...

Quoted 1 line

RDEPENDS_${PN} = "libfoo"

... RDEPENDS is for runtime dependencies specific packages and thus has _<package name> as suffix ($PN = bar in this case).

You also don't need the RDEPENDS_${PN} line in your recipe at all in normal
cases: if your app links with libfoo, the runtime dependency will be automatically added.

Jussi