From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Convert vala to new world staging
Date: Sat, 06 Mar 2010 06:58:40 -0800 [thread overview]
Message-ID: <1267887520.11175.17.camel@rex> (raw)
In-Reply-To: <F5DBF875-2CE0-4218-A2FD-45E83EE3AADD@vanille-media.de>
On Fri, 2010-03-05 at 17:56 +0100, Dr. Michael Lauer wrote:
> > All vala recipes currently complain about being lagacy stages. With a
> > lot of help from my friends I came up with this patch for
> > classes/vala.bbclass.
> >
> > diff --git a/classes/vala.bbclass b/classes/vala.bbclass
> > index 2633905..2c23efb 100644
> > --- a/classes/vala.bbclass
> > +++ b/classes/vala.bbclass
> > @@ -9,8 +9,8 @@ VALA_DONT_STAGE_VAPIS ?= "\(/config.vapi$\)\|\(/config.deps$\)"
> >
> > # .vapi and .deps files are arch independent and need to be present in the
> > # staging datadir for the native vala compiler
> > -do_stage_append() {
> > - 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
> > +do_install_append() {
> > + install -d ${D}${datadir}/vala/vapi
> > + for VALAFILE in `find . -name "*.vapi" | grep -v "$VALA_DONT_STAGE_VAPIS"`; do install -m 0644 ${VALAFILE} ${D}${datadir}/vala/vapi/; done
> > + for VALAFILE in `find . -name "*.deps" | grep -v "$VALA_DONT_STAGE_VAPIS"`; do install -m 0644 ${VALAFILE} ${D}${datadir}/vala/vapi/; done
> > }
>
> This will only work for vala-native. All non-native packages inheriting vala will then fail to install their
> .vapi files in STAGING_DATADIR_NATIVE, which is where vala-native expects them to be.
Something is very wrong with vala-native then :(
Target packages should not be installing things into the native sysroot.
The reason why is when we come to start using staging packages, these
staging packages are going to have a dependency on the specific build
system they were built on.
If these files are architecture independent I'd suggest putting them in
an architecture independent path (which native sysroot is not)
Cheers,
Richard
next prev parent reply other threads:[~2010-03-06 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 15:14 Convert vala to new world staging Sebastian Spaeth
2010-03-05 16:42 ` Koen Kooi
2010-03-05 16:56 ` Dr. Michael Lauer
2010-03-06 14:58 ` Richard Purdie [this message]
2010-03-06 16:25 ` 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=1267887520.11175.17.camel@rex \
--to=rpurdie@rpsys.net \
--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.