Skip to contentSkip to conversation

Another story of a non upstream user of poky

DISCUSSION Holger Hans Peter Freyther 5 participants 13 messages Jul 27, 2011

lore
Share & tools
lore
#0 lore raw

Hi,

todays story is adding a 'interfaces' to netbase.

$ touch sysmocom/recipes-core/netbase/netbase-4.45/alix/interfaces
$ vi sysmocom/recipes-core/netbase/netbase_4.45.bbappend
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
PRINC = "1"
$ bitbake netbase

So does it work? The answer is no. Why doesn't it work? meta-yocto already has a bbappend file? How to solve it? Use different names? Automatically add FILESPATH for bbappends?

comments?

holger

#1 lore raw

Op 27 jul. 2011, om 14:47 heeft Holger Hans Peter Freyther het volgende geschreven:

Quoted 11 lines

Hi,

todays story is adding a 'interfaces' to netbase.

$ touch sysmocom/recipes-core/netbase/netbase-4.45/alix/interfaces
$ vi sysmocom/recipes-core/netbase/netbase_4.45.bbappend
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
PRINC = "1"
Quoted 6 lines
$ bitbake netbase

So does it work? The answer is no. Why doesn't it work? meta-yocto already has a bbappend file? How to solve it? Use different names? Automatically add FILESPATH for bbappends?

touch oe-core/meta/recipes-core/netbase/netbase_4.45.bb to force a reparse. bbappends only get parsed if the main recipe changed.

#2 lore raw
Quoted 2 lines · Koen Kooi

touch oe-core/meta/recipes-core/netbase/netbase_4.45.bb to force a reparse. bbappends only get parsed if the main recipe changed.

thanks, the problem is with meta-yocto in this case, there is netbase_4.45.bbappend in there, so THISDIR is not what I think it is when using it, or such.

#8 lore raw
In reply to Holger Hans Peter Freyther
Quoted 3 lines · On Wednesday 27 July 2011 13:47:22 Holger Hans Peter Freyther wrote:

So does it work? The answer is no. Why doesn't it work? meta-yocto already has a bbappend file? How to solve it? Use different names? Automatically add FILESPATH for bbappends?

I'd be in favour of automatically handling this somehow, but there might be concerns that make that impractical, I'm not sure.

Anyway, the canonical method for doing this with OE-core/Poky, based on your example, is:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#3 lore raw
In reply to Holger Hans Peter Freyther
Quoted 3 lines · On Wednesday 27 July 2011 13:57:22 Holger Hans Peter Freyther wrote:

thanks, the problem is with meta-yocto in this case, there is netbase_4.45.bbappend in there, so THISDIR is not what I think it is when using it, or such.

THISDIR should be correct at parse time; if not, something's wrong. After that, it won't of course. (Hence my use of := in my example; I suspect your use of =. is why your example didn't work).

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#12 lore raw
In reply to Holger Hans Peter Freyther
Quoted 11 lines · Holger Hans Peter Freyther

Hi,

todays story is adding a 'interfaces' to netbase.

$ touch sysmocom/recipes-core/netbase/netbase-4.45/alix/interfaces
$ vi sysmocom/recipes-core/netbase/netbase_4.45.bbappend
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
PRINC = "1"
Quoted 8 lines
$ bitbake netbase

So does it work? The answer is no. Why doesn't it work? meta-yocto already has a bbappend file? How to solve it? Use different names? Automatically add FILESPATH for bbappends?

comments?

Set the layer priority for sysmocom/ higher than meta-yocto

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#4 lore raw
In reply to Paul Eggleton
Quoted 8 lines · Paul Eggleton
Quoted 3 lines · On Wednesday 27 July 2011 13:57:22 Holger Hans Peter Freyther wrote:

thanks, the problem is with meta-yocto in this case, there is netbase_4.45.bbappend in there, so THISDIR is not what I think it is when using it, or such.

THISDIR should be correct at parse time; if not, something's wrong. After that, it won't of course. (Hence my use of := in my example; I suspect your use of =. is why your example didn't work).

For koen I just wanted to day that I know that my bbappend was parsed (PRINC and bogus stuff has effect on parsing)

THISDIR is set by the netbase_4.45.bbappend of meta-yocto, I assume that this should not be done and one should use the form you proposed throughout the layers?

#9 lore raw
In reply to Paul Eggleton
Quoted 2 lines · Paul Eggleton

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

this works nicely, I think the THISDIR assignment should be removed from meta-yocto though. Now there appears to be one more bug, PACKAGE_ARCH is not set to the MACHINE_ARCH even after the right interfaces is used. Is that known?

#5 lore raw
In reply to Holger Hans Peter Freyther
Quoted 3 lines · On Wednesday 27 July 2011 14:08:16 Holger Hans Peter Freyther wrote:

THISDIR is set by the netbase_4.45.bbappend of meta-yocto, I assume that this should not be done and one should use the form you proposed throughout the layers?

Correct, and this has already been done in master.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#6 lore raw
Quoted 6 lines · Paul Eggleton
Quoted 3 lines · On Wednesday 27 July 2011 14:08:16 Holger Hans Peter Freyther wrote:

THISDIR is set by the netbase_4.45.bbappend of meta-yocto, I assume that this should not be done and one should use the form you proposed throughout the layers?

Correct, and this has already been done in master.

ah sorry, I should rebase my poky base.

#10 lore raw
In reply to Holger Hans Peter Freyther
Quoted 3 lines · On Wednesday 27 July 2011 14:13:52 Holger Hans Peter Freyther wrote:

Now there appears to be one more bug, PACKAGE_ARCH is
not set to the MACHINE_ARCH even after the right interfaces is used. Is that known?

Hmm, you're right, this is an omission. Presumably for meta-yocto this should be PACKAGE_ARCH_beagleboard = "${MACHINE_ARCH}" ?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#11 lore raw

Op 27 jul. 2011, om 15:17 heeft Paul Eggleton het volgende geschreven:

Quoted 7 lines · On Wednesday 27 July 2011 14:13:52 Holger Hans Peter Freyther wrote:
Quoted 3 lines

Now there appears to be one more bug, PACKAGE_ARCH is
not set to the MACHINE_ARCH even after the right interfaces is used. Is that known?

Hmm, you're right, this is an omission. Presumably for meta-yocto this should be PACKAGE_ARCH_beagleboard = "${MACHINE_ARCH}" ?

OE should be doing that automatically since something in SRC_URI is getting pulled from a machine specific dir.

#7 lore raw
In reply to Koen Kooi
Quoted 13 lines · Koen Kooi

Op 27 jul. 2011, om 14:47 heeft Holger Hans Peter Freyther het volgende geschreven:

Quoted 12 lines

todays story is adding a 'interfaces' to netbase.

$ touch sysmocom/recipes-core/netbase/netbase-4.45/alix/interfaces
$ vi sysmocom/recipes-core/netbase/netbase_4.45.bbappend
FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}-${PV}"], d)}:"
PRINC = "1"
$ bitbake netbase
Quoted 6 lines
Quoted 3 lines

So does it work? The answer is no. Why doesn't it work? meta-yocto already has a bbappend file? How to solve it? Use different names? Automatically add FILESPATH for bbappends?

touch oe-core/meta/recipes-core/netbase/netbase_4.45.bb to force a reparse. bbappends only get parsed if the main recipe changed.

Wrong, that bug has been fixed in bitbake! :)

Cheers,

Richard