From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: DEPENDS_virtclass-native = "libpng jpeg" not extended to libpng-native jpeg-native
Date: Tue, 11 Sep 2012 10:03:34 +0200 [thread overview]
Message-ID: <20120911080334.GD3465@jama.jama.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Hi,
in meta-openembedded/meta-oe/recipes-extended/libwmf/libwmf_0.2.8.4.bb:
DEPENDS_virtclass-native = "libpng jpeg"
DEPENDS = "libpng jpeg expat gtk+"
BBCLASSEXTEND = "native"
Did it work (at least at some point of time) that DEPENDS for
libwmf-native were expanded to libpng-native and jpeg-native?
Because now it does not:
OE tuna@shr ~/shr-core $ bitbake-diffsigs
stamps.1347348593/nokia900/x86_64-linux/libwmf-native-0.2.8.4-r1.do_configure.sigdata.315a83efebb27040d6bf0aaead16671e
stamps.1347348593/om-gta02/x86_64-linux/libwmf-native-0.2.8.4-r1.do_configure.sigdata.0f8349ada0c8a18a6d6ed7b7841ec955
Hash for dependent task libpng_1.2.49.bb.do_populate_sysroot changed
from 640001ee0530e51ef0aefb300c34f7dd to 7ba7d74a27e1e0af253ddac00a2be1c2
Hash for dependent task libjpeg-turbo_svn.bb.do_populate_sysroot changed
from 3fe6eae3a6fd1af40233d548680c5bab to ff852ac3d5e826ff74e68b5ddc4ac3e1
So native recipe depending on target checksum -> rebuilding with each
MACHINE switch.
I can fix it by:
DEPENDS_virtclass-native = "libpng-native jpeg-native"
but maybe there is more cases like this and this could be checked by
native.bbclass or something like that.
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2012-09-11 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 8:03 Martin Jansa [this message]
2012-09-11 9:03 ` DEPENDS_virtclass-native = "libpng jpeg" not extended to libpng-native jpeg-native Richard Purdie
2012-09-11 9:36 ` Martin Jansa
2012-09-11 10:07 ` Martin Jansa
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=20120911080334.GD3465@jama.jama.net \
--to=martin.jansa@gmail.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