From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: meta-toolchain question
Date: Thu, 21 Jul 2011 13:00:41 -0600 [thread overview]
Message-ID: <4E287759.3050806@mlbassoc.com> (raw)
When I build the meta-toolchain for my armv5te target, I see
some confusing paths. For example, why is the environment script named
/opt/poky/1.00+snapshot/environment-setup-armv5te-poky-linux-gnueabi
but the sysroot is named
/opt/poky/1.00+snapshot/sysroots/arm-poky-linux-gnueabi
Why isn't it
/opt/poky/1.00+snapshot/sysroots/armv5te-poky-linux-gnueabi
I even see some stranger paths, like these
/opt/poky/1.00+snapshot/sysroots/i686-pokysdk-linux/usr/lib/armv5te-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi
I would think it should be armv5te-poky-linux-gnueabi everywhere.
If I wanted to also have a meta-toolchain for armv7a, there would
be a clash since they both use the same sysroots.
Note: I sort of asked this question yesterday and the answer was
"use ADT". I don't see that ADT will solve this and I also find
ADT much to heavyweight for my customers who just want a simple
toolchain that matches their Poky-built system.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
reply other threads:[~2011-07-21 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E287759.3050806@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@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.