From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] buildman: Add a way to specific a full toolchain prefix
Date: Mon, 14 Mar 2016 10:56:24 -0600 [thread overview]
Message-ID: <56E6ED38.6050904@wwwdotorg.org> (raw)
In-Reply-To: <1457833833-11889-2-git-send-email-sjg@chromium.org>
On 03/12/2016 06:50 PM, Simon Glass wrote:
> At present buildman allows you to specify the directory containing the
> toolchain, but not the actual toolchain prefix. If there are multiple
> toolchains in a single directory, this can be inconvenient.
>
> Add a new 'toolchain-prefix' setting to the settings file, which allows
> the full prefix (or path to the C compiler) to be specified.
>
> Update the documentation to match.
Excellent, now the buildman config file does exactly what I want:-)
Tested-by: Stephen Warren <swarren@nvidia.com>
I tested the version already applied in u-boot-dm/buildman, which I
assume is the same as this:-)
next prev parent reply other threads:[~2016-03-14 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 1:50 [U-Boot] [PATCH v2 1/3] buildman: Allow branch names which conflict with directories Simon Glass
2016-03-13 1:50 ` [U-Boot] [PATCH v2 2/3] buildman: Add a way to specific a full toolchain prefix Simon Glass
2016-03-14 16:56 ` Stephen Warren [this message]
2016-03-20 0:25 ` Simon Glass
2016-03-13 1:50 ` [U-Boot] [PATCH v2 3/3] buildman: Clarify the use of -V Simon Glass
2016-03-14 16:56 ` Stephen Warren
2016-03-20 0:26 ` Simon Glass
2016-03-20 0:25 ` [U-Boot] [PATCH v2 1/3] buildman: Allow branch names which conflict with directories 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=56E6ED38.6050904@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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