Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jonas Danielsson <jonas.danielsson@lundinova.se>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] opkg-utils: extend to nativesdk
Date: Wed, 18 Apr 2012 22:27:49 +0200	[thread overview]
Message-ID: <20120418202749.GA7480@jkd-desktop> (raw)
In-Reply-To: <1334768201.24091.152.camel@ted>

On Wed, Apr 18, 2012 at 05:56:41PM +0100, Richard Purdie wrote:
> On Wed, 2012-04-18 at 18:12 +0200, Jonas Danielsson wrote:
> > Signed-off-by: Jonas Danielsson <jonas.danielsson@lundinova.se>
> > ---
> >  meta/recipes-devtools/opkg-utils/opkg-utils_git.bb |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> >
> > diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> > index 4fe4038..eb42eae 100644
> > --- a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> > +++ b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> > @@ -6,6 +6,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
> >                      file://opkg.py;beginline=1;endline=18;md5=15917491ad6bf7acc666ca5f7cc1e083"
> >  RDEPENDS_${PN} = "python"
> >  RDEPENDS_${PN}_virtclass-native = ""
> > +RDEPENDS_${PN}_virtclass-nativesdk = "python-nativesdk"
>
> Doesn't this happen automatically?
>

I am not a terribly experienced oe developer so I had an hard time figuring
that out :) Maybe someone here can help me with it.

When I did not have it and did 'bitbake -g opkg-utils-nativesdk' then
used grep on the resulting pn-depends.dot file I got:
"opkg-utils-nativesdk" -> "python" [style=dashed]

And doing the same procedure without it I got:
"opkg-utils-nativesdk" -> "python-nativesdk" [style=dashed]

But my toolchain works either way because python-nativesdk gets in
through: "gdb-cross-canadian-arm" -> "python-nativesdk"

So I'm not sure, is it needed or not?

> >  SRCREV = "16665959c330b5958c0f0f4624a9ca7f823f98de"
> >  PV = "0.1.8+git${SRCPV}"
> >  PR = "r1"
> > @@ -27,5 +28,5 @@ do_install() {
> >     oe_runmake PREFIX=${prefix} DESTDIR=${D} install
> >  }
> >
> > -BBCLASSEXTEND = "native"
> > +BBCLASSEXTEND = "native nativesdk"
> >  TARGET_CC_ARCH += "${LDFLAGS}"
>
> Cheers,
>
> Richard
>

Thanks!
Jonas

>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




      reply	other threads:[~2012-04-18 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 16:12 [PATCH] opkg-utils: extend to nativesdk Jonas Danielsson
2012-04-18 16:56 ` Richard Purdie
2012-04-18 20:27   ` Jonas Danielsson [this message]

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=20120418202749.GA7480@jkd-desktop \
    --to=jonas.danielsson@lundinova.se \
    --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