From: Khem Raj <raj.khem@gmail.com>
To: Virgilia Eigner <virgi200@gmx.de>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: External toolchain
Date: Wed, 28 Oct 2015 11:46:41 -0700 [thread overview]
Message-ID: <0D9FEC4F-ADB0-4A68-AD17-D9EF2580EEFC@gmail.com> (raw)
In-Reply-To: <C5143333-4B76-4AC2-B295-F63B89B4F14D@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
> On Oct 28, 2015, at 11:37 AM, Virgilia Eigner <virgi200@gmx.de> wrote:
>
> Hi,
>
> I am working on a image for my personal hardware.
> In this case I use to prefer my own toolchain (used before in buildroot).
> Now I am not sure how to proceed.
> Is it possible to include the old toolchain with a few chance setting in local.conf
> Or do i have to create my own Layer?
> How should i start with, are there some examples?
>
you can hook in external toolchains, e.g. look at https://github.com/MentorEmbedded/meta-sourcery
for some guidance
> -Yocto Version YP Core-Dizzy 1.7.2
> -My own customize hardware, with different interfaces
>
>
> best regards Lisa
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2015-10-28 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 18:37 External toolchain Virgilia Eigner
2015-10-28 18:46 ` Khem Raj [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 9:26 external toolchain Virgilia Eigner
2015-11-19 7:01 ` Khem Raj
2015-11-20 9:18 ` Virgilia Eigner
2014-03-28 10:20 External Toolchain Anjandeep Sahni
2014-03-28 16:42 ` Denys Dmytriyenko
2012-07-12 19:20 external toolchain Dallas Clement
2012-07-12 19:23 ` Chris Larson
2011-02-24 9:13 External toolchain Luca Bolognini
2011-02-23 11:49 Luca Bolognini
2011-02-23 19:28 ` Khem Raj
2011-02-24 4:07 ` Denys Dmytriyenko
2011-02-22 9:16 Luca Bolognini
2011-02-22 9:47 ` Ahsan, Noor
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=0D9FEC4F-ADB0-4A68-AD17-D9EF2580EEFC@gmail.com \
--to=raj.khem@gmail.com \
--cc=virgi200@gmx.de \
--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.