All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: Re: How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto?
Date: Wed, 01 Jun 2016 10:13:00 +0300	[thread overview]
Message-ID: <574E8AFC.9060207@reliableembeddedsystems.com> (raw)
In-Reply-To: <OFA057DFA2.53F4A083-ONC1257FC4.0052706B-C1257FC4.0052B04C@esa-grimma.de>

Hi,

On 05/31/2016 06:03 PM, S.Jaritz@esa-grimma.de
wrote:> Hej,
>
> I am looking for an example where is shown how to include an own library
> into the toolchain.
>
> Let's call the library "myLib". For it I created an recipe "myLib.bb"
> and added:
>
>     BBCLASSEXTEND = "native nativesdk"

Like this you can build a myLib-native (for your host - x86) version and
it should be added as an x86 library to your nativesdk.

see:

http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-BBCLASSEXTEND

>
> In my "local.conf" I added:
>
>     IMAGE_INSTALL_append = " myLib"
>
> When building the SDK by:
>
>     $ bitbake myTarget -c populate_sdk
>
> It produces a installer for the SDK and two manifest files. "myLib" is
> only included at the target manifest and not on the host. How can I
> include myLib on the host system?

Do you want myLib-native?

>
> The idea is, that a other person can build software on his system
> without the Yocto system. Only by using the toolchain he can generate
> binaries, which can be transferred and executed at the evalboard.

I guess you want something else. You want e.g. the ARM library myLib in
your sysroot plus maybe header files.

What happens if you create a recipe like a testcase for your library
which DEPENDS_append = " myLib" and then you IMAGE_INSTALL_append = "
myLib testmyLib", rebuild the image and populate_sdk?

>
>
> Regards!

Regards,

Robert

>
> PS: I put the question on stackoverflow:
>
http://stackoverflow.com/questions/37548851/how-to-include-a-own-libary-into-the-toolchainsdk-for-an-embeeded-linux-genera
>
>
>
> ------------------------------------------------------------
> ESA Elektroschaltanlagen Grimma GmbH
> Broner Ring 30
> 04668 Grimma
> Telefon: +49 3437 9211 176
> Telefax: +49 3437 9211 26
> E-Mail: s.jaritz@esa-grimma.de
> Internet: www.esa-grimma.de
>
>
> Geschäftsführer:
> Dipl.-Ing. Jörg Gaitzsch
> Jörg Reinker
>
> Sitz der Gesellschaft: Grimma
> Ust.-ID: DE 141784437
> Amtsgericht: Leipzig, HRB 5159
> Steuernummer: 238/108/00755
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten
> haben, informieren Sie bitte sofort den Absender und löschen Sie diese
> Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> Mail
> ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If
> you are
> not the intended recipient (or have received this e-mail in error) please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly
> forbidden.
>
>
> --
>

...To go faster, slow down. Everybody who knows about orbital mechanics
understands that.- Scott Cherf

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2016-06-01  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 15:03 How to include a own libary into the toolchain(SDK) for an embeeded Linux generated by Yocto? S.Jaritz
2016-06-01  7:13 ` Robert Berger [this message]
2016-06-01  7:47   ` Antwort: " S.Jaritz
2016-06-01  8:06   ` [Solved] " S.Jaritz

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=574E8AFC.9060207@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.com \
    --cc=yocto@yoctoproject.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.