From: Saul Wold <sgw@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}?
Date: Thu, 26 Jan 2012 17:28:02 -0800 [thread overview]
Message-ID: <4F21FDA2.5070803@linux.intel.com> (raw)
In-Reply-To: <CALbNGRS-WsE45UakTV5VE2T5bAxb1C2iWgPeN+Ys+OTx-i48Rw@mail.gmail.com>
On 01/26/2012 05:16 PM, Andreas Müller wrote:
> Since the staticdev update of insane.bbclass in oe-core I get
>
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libtiffdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpixbufdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libcomicsdocument.a'
> WARNING: QA Issue: non -staticdev package contains static .a library:
> evince path '/work/armv7a-angstrom-linux-gnueabi/evince-2.32.0-r1/packages-split/evince/usr/lib/evince/3/backends/libpdfdocument.a'
>
> I checked: the complete contents of /usr/lib/evince/3/backends go to
> evince package and I would like to move *.a to ${PN}-staticdev and
> *.la to ${PN}-dev but I don't understand: who is responsible for
> adding all this to ${PN}?
>
bitbake.conf defines where most files should go, but when you get files
in sub-directories, such as /usr/lib/evince/..., then the recipe needs
to do a little more work. If you look at the evince_2.32.0.bb, there
already is a FILES_${PN}-staticdev that adds some extensions, you need
to add this set of backends to that list, probably same with the .la to
the -dev package.
Sau!
> Regards
>
> Andreas
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2012-01-27 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 1:16 evince: who is responsible to pack all within usr/lib/evince/3/backends to ${PN}? Andreas Müller
2012-01-27 1:28 ` Saul Wold [this message]
[not found] ` <CALbNGRQ0+FDE7QisckBOCXBUspQiumZFLjPJYgRf87a1mqtHaw@mail.gmail.com>
2012-01-27 12:48 ` [oe] " Andreas Müller
2012-01-27 12:48 ` Andreas Müller
2012-01-27 15:22 ` [oe] " Saul Wold
2012-01-27 15:22 ` [OE-core] " Saul Wold
2012-01-27 23:16 ` [oe] " 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
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=4F21FDA2.5070803@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.