From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?
Date: Mon, 30 Jan 2012 15:45:43 -0800 [thread overview]
Message-ID: <4F272BA7.9060305@linux.intel.com> (raw)
In-Reply-To: <CALbNGRT4=F0cbdJ4oO1HmuhXnfmmmoBG1mWqziyDLM+vb-BKiw@mail.gmail.com>
On 01/28/2012 04:08 PM, Andreas Müller wrote:
> On Sat, Jan 28, 2012 at 11:46 PM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
>> On Sat, Jan 28, 2012 at 4:03 PM, Paul Eggleton
>> <paul.eggleton@linux.intel.com> wrote:
>>> On Saturday 28 January 2012 00:29:28 Andreas Müller wrote:
>>>> Have modified bitbake.conf here to
>>>>
>>>> PACKAGES = "${PN}-dbg ${PN}-dev ${PN}-staticdev ${PN} ${PN}-doc
>>>> ${PN}-locale"
>>>>
>>>> now I get the expected behavior.
>>>>
>>>> Will start a build from scratch for the night to see if there is some
>>>> fallout..
>>>
>>> We would need to be extremely careful before changing the default value of
>>> PACKAGES. I would strongly suggest you enable buildhistory when you do this so
>>> you can spot any changes easily, particularly in package content.
>>>
>> I am afraid you are so right: First build fallout is db. It shows that
>> the current implementation
>>
>> SOLIBS = ".so.*"
>> SOLIBSDEV = ".so"
>>
>> fails at least here. The main shared lib is found in -dev!
>>
>> Uhhh cold in here...
>>
> How about splitting bitbake.conf changes:
> 1. Now: move ${PN}-staticdev before ${PN}. This should not have the
> dramatic impact and makes it easier to fix new QA warnings.
> 2. (Much) later ${PN}-dev before ${PN}. This has huge impact and needs
> massive testing
>
From my understanding there are reasons (that I can't remember right
now) why ${PN} is where it is. As you note it might not be helpful in
this case anyways because of the ${BPN}/3.
Sau!
> Andreas
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2012-01-30 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALbNGRS-WsE45UakTV5VE2T5bAxb1C2iWgPeN+Ys+OTx-i48Rw@mail.gmail.com>
[not found] ` <4F21FDA2.5070803@linux.intel.com>
[not found] ` <CALbNGRQ0+FDE7QisckBOCXBUspQiumZFLjPJYgRf87a1mqtHaw@mail.gmail.com>
2012-01-27 12:48 ` [oe] evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}? Andreas Müller
2012-01-27 15:22 ` Saul Wold
2012-01-27 23:16 ` Andreas Müller
2012-01-27 23:29 ` Andreas Müller
2012-01-28 15:03 ` Paul Eggleton
2012-01-28 22:46 ` Andreas Müller
2012-01-29 0:08 ` Andreas Müller
2012-01-30 23:45 ` Saul Wold [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=4F272BA7.9060305@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