From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman and multiple toolchains?
Date: Thu, 23 Apr 2015 09:07:47 -0400 [thread overview]
Message-ID: <20150423130747.GY16702@bill-the-cat> (raw)
Hey,
So I'm merging (or rather have merged and will push shortly) the ARMv7-M
support. You can't build this with your normal arm-linux toolchain. Is
there some way in buildman to be able to say, roughly:
[toolchain]
arm: /usr/bin/arm-linux-gnueabi
armnone: /usr/bin/arm-none-eabi
[toolchain-alias]
stm32f429-discovery: armnone
And have the 'arm' toolchain used normally for arm but 'armnone' used
for the stm32f429-discovery board?
Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150423/4a5fb89c/attachment.sig>
next reply other threads:[~2015-04-23 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 13:07 Tom Rini [this message]
2015-04-23 18:44 ` [U-Boot] buildman and multiple toolchains? Simon Glass
2015-04-23 18:57 ` Tom Rini
2015-04-23 19:22 ` Simon Glass
2015-04-23 19:26 ` Tom Rini
2015-04-23 19:35 ` Simon Glass
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=20150423130747.GY16702@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox