From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: a38e7ff2810e55455c7ff7b01d4882344b420e18 breaks build and packaged-staging, among other things
Date: Sun, 25 Apr 2010 21:38:24 +0200 [thread overview]
Message-ID: <hr25nh$nft$1@dough.gmane.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Looking at
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=a38e7ff2810e55455c7ff7b01d4882344b420e18
I see:
- -do_stage_append() {
+vala_do_stage_vapi() {
install -d ${STAGING_DATADIR_NATIVE}/vala/vapi
for VALAFILE in `find . -name "*.vapi" | grep -v
"$VALA_DONT_STAGE_VAPIS"`; do install -m 0644 ${VALAFILE}
${STAGING_DATADIR_NATIVE}/vala/vapi/; done
for VALAFILE in `find . -name "*.deps" | grep -v
"$VALA_DONT_STAGE_VAPIS"`; do install -m 0644 ${VALAFILE}
${STAGING_DATADIR_NATIVE}/vala/vapi/; done
}
+
+EXPORT_FUNCTIONS do_stage_vapi
+
+addtask stage_vapi after do_populate_staging before do_package
Attentive readers will see that anything using vala.bbclass will now
stage things needed for downstream dependencies outside of do_stage
*and* do_install()
This means that doing
bitbake something-depending-on-vala-stuf
is now broken because bitbake will run
something-depending-on-vala-stuf.do_configure and compile after
vala-stuff.do_populate_staging and the vapi files will NOT be there.
The other problem is that the packaged-staging packages won't contain
the vapi files, so rebuilding staging it broken as well.
So all in all: please revert that.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL1JowMkyGM64RGpERAnRZAJ4qt9DIkXen+f8KTqp9yWE7YZfibQCdHUAo
mS3KolPmIvCmOv1F4GHzPS4=
=UAn/
-----END PGP SIGNATURE-----
next reply other threads:[~2010-04-25 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 19:38 Koen Kooi [this message]
2010-04-25 19:52 ` a38e7ff2810e55455c7ff7b01d4882344b420e18 breaks build and packaged-staging, among other things Graeme Gregory
2010-04-25 22:35 ` Michael 'Mickey' Lauer
2010-04-26 6:36 ` Koen Kooi
2010-04-26 8:11 ` Michael 'Mickey' Lauer
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='hr25nh$nft$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.