From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yevhen Kyriukha <kirgene@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: Multiple *.bbappend files support
Date: Mon, 15 Apr 2013 12:47:12 +0100 [thread overview]
Message-ID: <1366026432.8670.32.camel@ted> (raw)
In-Reply-To: <CADV-EXF-_FHVhfXje=4z7ayCpEOYNCp74=3wVpxKR7UZufUH_A@mail.gmail.com>
On Mon, 2013-04-15 at 14:34 +0300, Yevhen Kyriukha wrote:
> 2013/4/15 Richard Purdie <richard.purdie@linuxfoundation.org>:
> > On Mon, 2013-04-15 at 13:37 +0300, Yevhen Kyriukha wrote:
> >> Great, thanks!
> >> Best regards,
> >> Yevhen
> >>
> >>
> >> 2013/4/15 Koen Kooi <koen@dominion.thruhere.net>:
> >> >
> >> > Op 15 apr. 2013, om 12:26 heeft Yevhen Kyriukha <kirgene@gmail.com> het volgende geschreven:
> >> >
> >> >> Is there a way to use multiple *.bbappend files in different layers?
> >> >>
> >> >> I'm using meta-raspberrypi and my own layer.
> >> >> Both extend base-files with *.bbappend and both have PRINC = "1".
> >> >> But only first of *.bbappend files applied (that is in meta-raspberrypi).
> >> >> PR of base-files also increments by one (not by two).
> >> >
> >> > Yeah, try to make all bbappends use:
> >> >
> >> > PRINC := "${@int(PRINC) + 1}"
> >> >
> >
> > I'd just add that with the PR server now in use, the need to add this
> > PRINC stuff should be removed...
> >
> > Cheers,
> >
> > Richard
> >
>
> And what does it mean? What do I need to write in bbappend instead of PRINC?
Nothing. The system automatically detects changes in the metadata
through the sstate checksum and then automatically changed PR as
needed.
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#working-with-a-pr-service
Cheers,
Richard
prev parent reply other threads:[~2013-04-15 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 10:26 Multiple *.bbappend files support Yevhen Kyriukha
2013-04-15 10:33 ` Koen Kooi
2013-04-15 10:37 ` Yevhen Kyriukha
2013-04-15 11:23 ` Richard Purdie
2013-04-15 11:34 ` Yevhen Kyriukha
2013-04-15 11:47 ` Richard Purdie [this message]
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=1366026432.8670.32.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=kirgene@gmail.com \
--cc=koen@dominion.thruhere.net \
--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