Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: native recipes use legacy staging.
Date: Wed, 31 Mar 2010 08:32:39 +0200	[thread overview]
Message-ID: <houqa6$sei$1@dough.gmane.org> (raw)
In-Reply-To: <18e217241003301757i23125ed4g3bb55a795ff5db02@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31-03-10 02:57, C Michael Sundius wrote:
> why does the native.bbclass force the use of legacy staging?
> 
> also how can I override this. I tried go use create my own
> 
> do_stage() {
>    :
> }
> 
> function in my recipe, but the one in the class was still used.
> 
> My issue is that my install function does not use make at all, nor autotools
> 
> so the do_stage_native() call [from do_stage() ] fails.

Try:

PR = "031110"

BBCLASSEXTEND = "native nativesdk"

SRC_URI = "file:///home/sundism/src/mkimage-tools"

S = ${WORKDIR}/mkimage-tools

do_compile() {
        :
}


do_install() {
        install  -m 0755 -d ${D}${bindir}
        install  -m 0755 ${S}/bin/imgen ${D}${bindir}/imgen
        install  -m 0755 -d ${D}${datadir}
        install  -m 0755 -d ${D}${datadir}/LxLoad
        install  -m 0644 ${S}/share/LxLoad/LxLoad2_cronus.img \
                ${D}${datadir}/LxLoad/LxLoad2_cronus.img
}

NATIVE_INSTALL_WORKS = "1"

regards,

Koen



> 
> thanks
> 
> see my [smiple] recipe attached:
> 
> 
> 
> PR = "031110"
> 
> BBCLASSEXTEND = "native nativesdk"
> 
> #SRC_URI = "http://sauscupoe01.cisco.com/cisco/mkimage-tools-${PR}.tar.gz"
> SRC_URI = "file:///home/sundism/src/mkimage-tools"
> 
> S = ${WORKDIR}/mkimage-tools
> 
> do_compile() {
>         :
> }
> 
> 
> do_install() {
>         install  -m 0755 -d ${STAGING_BINDIR}
>         install  -m 0755 ${S}/bin/imgen ${bindir}/imgen
>         install  -m 0755 -d ${datadir}
>         install  -m 0755 -d ${datadir}/LxLoad
>         install  -m 0644 ${S}/share/LxLoad/LxLoad2_cronus.img \
>                 ${datadir}/LxLoad/LxLoad2_cronus.img
> }
> 
> do_stage() {
>         :
> }

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLsuyGMkyGM64RGpERAio6AJ9PjMeb+iq2Am3tjN+P+19s0ptidACfYTEs
FYAeax4moDD7wBXztg7mpTQ=
=ETCW
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-03-31  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  0:57 native recipes use legacy staging C Michael Sundius
2010-03-31  6:32 ` Koen Kooi [this message]
2010-03-31 17:10   ` C Michael Sundius

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='houqa6$sei$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox