diff options
author | Masahiro Yamada <yamada.m@jp.panasonic.com> | 2014-03-03 11:06:19 +0900 |
---|---|---|
committer | Tom Rini <trini@ti.com> | 2014-03-04 12:15:31 -0500 |
commit | db5b339cca2f7b7824372f02932c3d7c24a34ed3 (patch) | |
tree | 379ea078c1df300b6710fbf82f29afe53c9c9ed0 /tools/bddb/brlog.php | |
parent | 1ec8b4efce83e7739720afbbf6a19937704eb8d5 (diff) | |
download | u-boot-imx-db5b339cca2f7b7824372f02932c3d7c24a34ed3.zip u-boot-imx-db5b339cca2f7b7824372f02932c3d7c24a34ed3.tar.gz u-boot-imx-db5b339cca2f7b7824372f02932c3d7c24a34ed3.tar.bz2 |
kbuild: add "cross_tools" target to build tools for the target
Programs in tools/ directory are usually built for the host.
But some of them (mkimage, dumpimge, gen_eth_addr, etc.) are
useful on the target OS too.
Actually, prior to Kbuild, U-Boot could build tools for
the target like follows:
$ make <target_board>_config
$ export CROSS_COMPILE=<cross_gcc_prefix>
$ make HOSTCC=${CROSS_COMPILE}gcc HOSTSTRIP=${CROSS_COMPILE}strip tools
In Kbuild, we can no longer replace HOSTCC at the command line.
In order to get back that feature, this commit adds "cross-tools" target.
Usage:
Build tools for the host
$ make CROSS_COMPILE=<cross_gcc_prefix> tools
Build tools for the target
$ make CROSS_COMPILE=<cross_gcc_prefix> cross_tools
Besides, "make cross_tools" strip tools programs because we
generally expect smaller storages on embedded systems.
Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Reported-by: Heiko Schocher <hs@denx.de>
Cc: Wolfgang Denk <wd@denx.de>
Cc: Tom Rini <trini@ti.com>
Tested-by: Heiko Schocher <hs@denx.de>
Acked-by: Heiko Schocher <hs@denx.de>
Diffstat (limited to 'tools/bddb/brlog.php')
0 files changed, 0 insertions, 0 deletions