From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Prebuilt toolchains
Date: Tue, 17 Nov 2009 08:34:53 +0100 [thread overview]
Message-ID: <hdtjmt$rcf$1@ger.gmane.org> (raw)
In-Reply-To: <4AFAEDC3.80404@mlbassoc.com>
On 11-11-09 18:00, Gary Thomas wrote:
> I'd like to use my own toolchains when building OpenEmbedded.
> I've tried to follow the information at:
> http://docs.openembedded.org/usermanual/usermanual.html#commonuse_prebuilt_toolchain
>
> It's a bit terse and confusing, so I'm just trying to see
> what I need (I think the section tries to discuss too many
> concepts at once)
If you're using angstrom and want to use a prebuilt CSL toolchain, you
only need to add this to local.conf (I suspect thunderbird will linewrap
it):
# Black magic to automatically set SDK_PATH out of PATH - don't touch this!
# Works with pretty much any external toolchain, like CS Lite or MV Pro 5
# Handles cross-toolchain vs. native toolchain
# SDK_PATH can be overwritten externally by META_SDK_PATH, e.g. for SDK
TOOLCHAIN_SYSPATH = "${@bb.data.getVar('TARGET_ARCH', d, 1) !=
bb.data.getVar('BUILD_ARCH', d, 1) and
os.path.abspath(os.path.dirname(bb.which(bb.data.getVar('PATH', d, 1),
bb.data.getVar('TARGET_PREFIX', d,
1)+'cpp'))+'/../'+bb.data.getVar('TARGET_SYS', d, 1)) or ''}"
TOOLCHAIN_PATH = "${@bool(bb.data.getVar('TOOLCHAIN_SYSPATH', d, 1)) and
(os.path.exists(bb.data.getVar('TOOLCHAIN_SYSPATH', d, 1)) and
os.path.dirname(bb.data.getVar('TOOLCHAIN_SYSPATH', d, 1)) or
bb.fatal('No valid toolchain in PATH')) or ''}"
SDK_PATH = "${@[bb.data.getVar('TOOLCHAIN_PATH', d, 1),
bb.data.getVar('META_SDK_PATH', d,
1)][bool(bb.data.getVar('META_SDK_PATH', d, 1))]}"
# Set the necessary variables to use binary CodeSourcery Lite
TARGET_VENDOR = "-none"
TARGET_CPPFLAGS_append = " -I${SDK_PATH}/${TARGET_SYS}/libc/usr/include "
TARGET_LDFLAGS_prepend = " -L${SDK_PATH}/${TARGET_SYS}/libc/lib
-Wl,-rpath-link,${SDK_PATH}/${TARGET_SYS}/libc/lib "
TOOLCHAIN_TYPE = "external"
TOOLCHAIN_BRAND = "csl"
regards,
Koen
next prev parent reply other threads:[~2009-11-17 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 17:00 Prebuilt toolchains Gary Thomas
2009-11-11 20:39 ` Chris Conroy
2009-11-11 21:07 ` Gary Thomas
2009-11-11 21:29 ` Chris Conroy
2009-11-13 14:06 ` Gary Thomas
2009-11-13 15:57 ` Chris Conroy
2009-11-13 17:25 ` Gary Thomas
2009-11-13 18:41 ` Chris Conroy
2009-11-13 23:00 ` Gary Thomas
2009-11-16 22:40 ` Gary Thomas
2009-11-17 3:12 ` Mike Turquette
2009-11-17 7:34 ` Koen Kooi [this message]
2009-11-18 13:40 ` Gary Thomas
2009-11-18 15:29 ` Gary Thomas
2009-11-18 23:24 ` Gary Thomas
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='hdtjmt$rcf$1@ger.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 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.