How do we get programs into sysroots?

How do we get programs into sysroots?

[Joel A Fernandes]

I have added a recipe for mkcard script to oe-core/meta/meta-devtools
as follows:

DESCRIPTION = "A tool to format SD Cards correctly"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
SECTION = "base"
SRC_URI = "file://mkcard.txt \
           file://COPYING.patch"
PR = "r3"

do_configure() {
        install -m 0644 ${WORKDIR}/mkcard.txt ${S}/
}

do_install() {
        install -d ${D}${base_sbindir}
        install -m 0755 ${S}/mkcard.txt ${D}${base_sbindir}/mkcard
}

BBCLASSEXTEND = "native"
---

Everything works fine, but I don't see 'mkcard' in /sbin in sysroots
directory. I'd like to install it there. I tried looking at other
scripts to see the right way to do it but I'm not sure of a clean way
to do so. I looked at the staging.bbclass and it seems to only pickup
libs and headers.

Appreciate any help or pointers to posts/documentation

Thanks,
Joel

Re: How do we get programs into sysroots?

[Chris Larson]

On Sun, Aug 28, 2011 at 1:07 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
> DESCRIPTION = "A tool to format SD Cards correctly"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
> SECTION = "base"
> SRC_URI = "file://mkcard.txt \
>           file://COPYING.patch"
> PR = "r3"
>
> do_configure() {
>        install -m 0644 ${WORKDIR}/mkcard.txt ${S}/
> }
>
> do_install() {
>        install -d ${D}${base_sbindir}
>        install -m 0755 ${S}/mkcard.txt ${D}${base_sbindir}/mkcard
> }
>
> BBCLASSEXTEND = "native"
> ---
>
> Everything works fine, but I don't see 'mkcard' in /sbin in sysroots
> directory. I'd like to install it there. I tried looking at other
> scripts to see the right way to do it but I'm not sure of a clean way
> to do so. I looked at the staging.bbclass and it seems to only pickup
> libs and headers.

When using a custom do_install, with BBCLASSEXTEND, afaik you need to
set NATIVE_INSTALL_WORKS = "1" to get its files into the sysroot for
the native version.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: How do we get programs into sysroots?

[Richard Purdie]

On Sun, 2011-08-28 at 13:45 -0700, Chris Larson wrote:
> On Sun, Aug 28, 2011 at 1:07 PM, Joel A Fernandes <agnel.joel@gmail.com> wrote:
> > DESCRIPTION = "A tool to format SD Cards correctly"
> > LICENSE = "GPLv2"
> > LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
> > SECTION = "base"
> > SRC_URI = "file://mkcard.txt \
> >           file://COPYING.patch"
> > PR = "r3"
> >
> > do_configure() {
> >        install -m 0644 ${WORKDIR}/mkcard.txt ${S}/
> > }
> >
> > do_install() {
> >        install -d ${D}${base_sbindir}
> >        install -m 0755 ${S}/mkcard.txt ${D}${base_sbindir}/mkcard
> > }
> >
> > BBCLASSEXTEND = "native"
> > ---
> >
> > Everything works fine, but I don't see 'mkcard' in /sbin in sysroots
> > directory. I'd like to install it there. I tried looking at other
> > scripts to see the right way to do it but I'm not sure of a clean way
> > to do so. I looked at the staging.bbclass and it seems to only pickup
> > libs and headers.
> 
> When using a custom do_install, with BBCLASSEXTEND, afaik you need to
> set NATIVE_INSTALL_WORKS = "1" to get its files into the sysroot for
> the native version.

For OE-dev you do but this shouldn't be necessary any more with OE-Core
since there is no legacy staging.

In this case I wonder if the -native version or the target version is
being run? We only install libs and headers for the target version but
the binaries should be present for the -native recipe and be installed
to the native sysroot...

Cheers,

Richard

Re: How do we get programs into sysroots?

[Joel A Fernandes]

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Hi Richard

Thanks for your email.

Forgive the top post due to the limitations of my phone.

This script should run as native. In this case what steps do we take to
ensure the binaries get installed to the native sysroots path?

Thanks,
Joel

On Aug 28, 2011 4:54 PM, "Richard Purdie" <
richard.purdie@linuxfoundation.org> wrote:

On Sun, 2011-08-28 at 13:45 -0700, Chris Larson wrote:
> On Sun, Aug 28, 2011 at 1:07 PM, Joel A Fer...
For OE-dev you do but this shouldn't be necessary any more with OE-Core
since there is no legacy staging.

In this case I wonder if the -native version or the target version is
being run? We only install libs and headers for the target version but
the binaries should be present for the -native recipe and be installed
to the native sysroot...

Cheers,

Richard




_______________________________________________
Openembedded-core mailing list
Openembedded-core@...

[-- Attachment #2: Type: text/html, Size: 1267 bytes --]

Re: How do we get programs into sysroots?

[Joel A Fernandes]

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

Thanks a lot, i'll try this.

Regards,
Joel

On Aug 28, 2011 3:46 PM, "Chris Larson" <clarson@kergoth.com> wrote:

On Sun, Aug 28, 2011 at 1:07 PM, Joel A Fernandes <agnel.joel@gmail.com>
wrote:
> DESCRIPTION = "A t...
When using a custom do_install, with BBCLASSEXTEND, afaik you need to
set NATIVE_INSTALL_WORKS = "1" to get its files into the sysroot for
the native version.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics


_______________________________________________
Openembedded-core mailing list
Openembedded-core@li...

[-- Attachment #2: Type: text/html, Size: 992 bytes --]