From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Kbuild: allow building tools without board configuration
Date: Mon, 31 Mar 2014 11:16:28 -0400 [thread overview]
Message-ID: <20140331151628.GS16360@bill-the-cat> (raw)
In-Reply-To: <1396254831-27972-1-git-send-email-yamada.m@jp.panasonic.com>
On Mon, Mar 31, 2014 at 05:33:51PM +0900, Masahiro Yamada wrote:
> Prior to Kbuild, U-Boot could build under tools/ directory
> withour configuring for a specific board.
>
> That feature was lost when switching to Kbuild.
>
> This patch revives it again by adding a make target "tools-only".
>
> Usage:
> $ make tools-only
>
> Neither board configuration nor cross compiler are required to
> build host tools.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Suggested-by: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: Tom Rini <trini@ti.com>
Problem is that we make enabling the signature code (which adds more
deps on the host) based on the config, and this was intentional. So
I'm not sure if we want to do this exactly, at least right now.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140331/935261f4/attachment.pgp>
next prev parent reply other threads:[~2014-03-31 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 8:33 [U-Boot] [PATCH] Kbuild: allow building tools without board configuration Masahiro Yamada
2014-03-31 10:07 ` Alexey Brodkin
2014-03-31 15:16 ` Tom Rini [this message]
2014-03-31 15:24 ` Alexey Brodkin
2014-03-31 15:31 ` Tom Rini
2014-03-31 15:39 ` Alexey Brodkin
2014-03-31 15:47 ` Tom Rini
2014-03-31 15:47 ` [U-Boot] " Tom Rini
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=20140331151628.GS16360@bill-the-cat \
--to=trini@ti.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