bbappend

bbappend

[Jaap de Jong]

Hi all!

I need some help concerning bbappend.
I've created a bbappend file:

    FILESEXTRAPATHS := "${THISDIR}/files"
    SRC_URI += "file://xyzzy.patch"

If I run a bitbake it complains about missing ..../xyzzy.patch
When I change the bbappend file to this:

    SRC_URI += "file:///absolute-path-to-the-file/files/xyzzy.patch"

then everything works fine...
(As a workaround this will do)

Any help is appreciated!!
Jaap

bbappend

[Jaap de Jong]

Hi all!

I need some help concerning bbappend.
I've created a bbappend file:

    FILESEXTRAPATHS := "${THISDIR}/files"
    SRC_URI += "file://xyzzy.patch"

If I run a bitbake it complains about missing ..../xyzzy.patch
When I change the bbappend file to this:

    SRC_URI += "file:///absolute-path-to-the-file/files/xyzzy.patch"

then everything works fine...
(As a workaround this will do)

Any help is appreciated!!
Jaap

Re: bbappend

[Paul Eggleton]

On Tuesday 12 July 2011 09:58:01 Jaap de Jong wrote:
> I need some help concerning bbappend.
> I've created a bbappend file:
> 
>     FILESEXTRAPATHS := "${THISDIR}/files"
>     SRC_URI += "file://xyzzy.patch"
> 
> If I run a bitbake it complains about missing ..../xyzzy.patch
> When I change the bbappend file to this:
> 
>     SRC_URI += "file:///absolute-path-to-the-file/files/xyzzy.patch"

FILESEXTRAPATHS is only available in oe-core. For classic OE you need to use 
something like:

THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
FILESPATHBASE_prepend := "${THISDIR}/files:"

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: bbappend

[Chris Verges]

On Tue, Jul 12, 2011 at 10:42:53AM +0100, Paul Eggleton wrote:
> FILESEXTRAPATHS is only available in oe-core. For classic OE you need
> to use something like:
> 
> THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
> FILESPATHBASE_prepend := "${THISDIR}/files:"

Hi Paul,

Thanks for clarifying and proposing a workaround.  It looks like PRINC
is similar, where it is only available in oe-core.  It seems like the
code related to incrementing the PR variable is a several-line fix, so
is this something that can be abstracted into a class file in the
local-overlay?

Thanks again,
Chris

Re: bbappend

[Paul Eggleton]

On Tuesday 12 July 2011 15:08:47 Chris Verges wrote:
> Thanks for clarifying and proposing a workaround.  It looks like PRINC
> is similar, where it is only available in oe-core.  It seems like the
> code related to incrementing the PR variable is a several-line fix, so
> is this something that can be abstracted into a class file in the
> local-overlay?

Possibly, however as a general suggestion I would recommend moving things over 
to being based on oe-core if at all possible. I realise this is not going to 
be practical for everyone in the short term, however OE classic will stop 
being maintained at some point in the near future, so the sooner you move the 
better - plus you get to take advantage of the additional features and 
cleanups in oe-core as well.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: bbappend

[Chris Verges]

On Tue, Jul 12, 2011 at 03:18:50PM +0100, Paul Eggleton wrote:
> Possibly, however as a general suggestion I would recommend moving
> things over to being based on oe-core if at all possible. I realise
> this is not going to be practical for everyone in the short term,
> however OE classic will stop being maintained at some point in the
> near future, so the sooner you move the better - plus you get to take
> advantage of the additional features and cleanups in oe-core as well.

I'd love to.  My most recent project is just starting out, so it's a
good time to make the switch.  Are there any good references for
performing a migration?

Thanks,
Chris

Re: bbappend

[Paul Eggleton]

On Tuesday 12 July 2011 15:31:01 you wrote:
> On Tue, Jul 12, 2011 at 03:18:50PM +0100, Paul Eggleton wrote:
> > Possibly, however as a general suggestion I would recommend moving
> > things over to being based on oe-core if at all possible. I realise
> > this is not going to be practical for everyone in the short term,
> > however OE classic will stop being maintained at some point in the
> > near future, so the sooner you move the better - plus you get to take
> > advantage of the additional features and cleanups in oe-core as well.
> 
> I'd love to.  My most recent project is just starting out, so it's a
> good time to make the switch.  Are there any good references for
> performing a migration?

We're rather lacking in oe-core specific documentation right now; however, you 
should be able to just grab oe-core and get started with it fairly easily:

 https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core

If you have any questions feel free to post them on the oe-core list:

 http://lists.linuxtogo.org/mailman/listinfo/openembedded-core

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

bbappend

[Jaap de Jong]

Hi All,

I want to make use of a standard oe package but I don't want it to be 
started at boot time.
Is there a way to disable update-rc.d (INITSCRIPT_*) from within a bbappend?

Thanks!
Jaap