From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/7] bitbake.conf: Add PACKAGE_BEFORE_PN to PACKAGES
Date: Fri, 29 Jun 2012 14:59:27 -0700 [thread overview]
Message-ID: <4FEE253F.805@linux.intel.com> (raw)
In-Reply-To: <CAMKF1so_1JQY-4eRWZ8Xkq4ixQ7cCmCSVAEohtjRJEFd9KoZiA@mail.gmail.com>
On 06/29/2012 02:52 PM, Khem Raj wrote:
>
>
> On Friday, June 29, 2012, Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>> wrote:
> > By doing this we can easily add addtional packages that can be
> > greedy before PN, but after some of the other standard packages.
> >
> > This will also allow us to simplify the lib_package class to set
> > this variable.
> >
> > Signed-off-by: Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>>
> > ---
> > meta/conf/bitbake.conf | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> > index 9377ee6..df4907e 100644
> > --- a/meta/conf/bitbake.conf
> > +++ b/meta/conf/bitbake.conf
> > @@ -254,7 +254,8 @@ SOLIBSDEV_darwin = ".dylib"
> > SOLIBSDEV_darwin8 = ".dylib"
> > SOLIBSDEV_darwin9 = ".dylib"
> >
> > -PACKAGES = "${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc
> ${PN}-locale ${PN}"
> > +PACKAGE_BEFORE_PN ?= ""
> > +PACKAGES = "${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc
> ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}"
> > PACKAGES_DYNAMIC = "${PN}-locale-*"
> > FILES = ""
> >
>
>
> Can it appear at the beginning before pn-dbg?
> Then you could just prepend I don't think any of those predefined
> packages will have anything of interest that's in pn-bin
No that's won't work since pn-dev wants to get -config binaries and
sometimes there are other binaries that pn-dev wants, I did try that
initially, by having -bin in front with =+ and got failures.
This has been a tricky set of changes to deal with.
Sau!
> > --
> > 1.7.10.4
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-06-29 22:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 21:21 [PATCH 0/7] Simplify lib_package Saul Wold
2012-06-29 21:21 ` [PATCH 1/7] bitbake.conf: Add PACKAGE_BEFORE_PN to PACKAGES Saul Wold
2012-06-29 21:52 ` Khem Raj
2012-06-29 21:59 ` Saul Wold [this message]
2012-06-29 22:09 ` Khem Raj
2012-06-29 22:09 ` Khem Raj
2012-06-29 22:16 ` Saul Wold
2012-06-30 2:51 ` Khem Raj
2012-06-29 21:21 ` [PATCH 2/7] lib_package: use PACKAGE_BEFORE_PN Saul Wold
2012-06-29 21:21 ` [PATCH 3/7] libacpi: use lib_package bbclass Saul Wold
2012-06-29 21:21 ` [PATCH 4/7] pulseaudio: " Saul Wold
2012-06-29 21:21 ` [PATCH 5/7] db: " Saul Wold
2012-06-29 21:21 ` [PATCH 6/7] gnutls: " Saul Wold
2012-06-29 21:21 ` [PATCH 7/7] speex: " Saul Wold
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=4FEE253F.805@linux.intel.com \
--to=sgw@linux.intel.com \
--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