All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: virtclass_install prepend
Date: Tue, 07 Sep 2010 14:57:58 +0100	[thread overview]
Message-ID: <1283867878.26335.305.camel@rex> (raw)
In-Reply-To: <20100906201144.GA8176@rhein.zuhause.netz>

On Mon, 2010-09-06 at 22:11 +0200, Henning Heinold wrote:
> > >> The code is:
> > >> do_install_virtclass-native_prepend() {
> > >>         install -d ${D}${datadir}/dbus
> > >>        install -m 0644 dbus-bus-introspect.xml ${D}${datadir}/dbus
> > >> }
> > >>
> > >> Actually if the standard do_install needs to be changed, it generally
> > >> raises some alarms with me.
> > >> Why would we need to install something that the package normally does
> > >> not install?
> > >> (of course this could be a bug in the package, but then I would prefer
> > >> a patch that we also try to push upstream).
> > >>
> > >
> > > Agreed, that is odd.  If it's something that dbus using things might need,
> > > why is it only prepended for the native version, and as you say, why is it
> > > not installed by the upstream install target.  I'd do a git blame and figure
> > > out who added that and ask them :)
> > > --
> > 
> > Henning,
> > Git blame gives your name as the person who created those lines.
> > Care to comment?
> > 
> > Frans
>
> if I remember correctly this file is generated in the build process. But somehow
> in the later versions of dbus-glib there is somehow an error so this file gets not installed
> at all in the native variant. So I did it per hand.

I suspect that code could well have come from Poky. In this case the
native recipe generates a file which is then used by the target builds.
It can't be generated in the target recipe as that would mean running
target binaries.

So it is in fact a perfectly valid thing to do in this case.

Cheers,

Richard




  reply	other threads:[~2010-09-07 13:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 11:29 virtclass_install prepend Frans Meulenbroeks
2010-08-19 16:15 ` Chris Larson
2010-08-19 19:14   ` Frans Meulenbroeks
2010-09-06  3:50     ` Khem Raj
2010-09-06  7:41       ` Frans Meulenbroeks
2010-09-06 13:54         ` Chris Larson
2010-09-06 16:25           ` Khem Raj
2010-09-06 16:35           ` Frans Meulenbroeks
2010-09-06 20:11             ` Henning Heinold
2010-09-07 13:57               ` Richard Purdie [this message]
2010-09-08  0:24                 ` Khem Raj

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=1283867878.26335.305.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.