From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild/makefile: allow building host tools separately
Date: Mon, 31 Mar 2014 10:43:37 +0900 [thread overview]
Message-ID: <20140331104335.DB68.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <1396043927.3876.6.camel@abrodkin-8560l>
Hi Alexey,
> >
> > This may be the similar discussion to
> > http://u-boot.10912.n7.nabble.com/U-Boot-could-not-cross-compile-u-boot-tools-td174911.html
>
> It looks not that relevant to me.
> For example even before switching U-Boot to Kbuild it was not possible
> to build host tools simply without patching sources/headers or
> configuring real target. Or I might be missing something here.
Sorry, I should have explained it more exactly.
What I wanted you to refer is Wolfgang's comment in that thread.
This part:
Wolfgang wrote:
> I'm not really hapy with the additional CROSS_BUILD_TOOLS paramert -
> but this may be a matter of taste, so the following is just a thought
> and a question:
>
> Would it make more sense to provide a sparate make target instead?
>
> Say, something like this:
>
> Build tools for host
> make CROSS_COMPILE=<your_gcc_prefix tools
> Build tools for target
> make CROSS_COMPILE=<your_gcc_prefix cross_tools
>
> ?
And then we chose a new make target "cross_tools"
rather than a new option "CROSS_BUILD_TOOLS=1".
That is similar to what is happening here.
I wanted to show retionale why a make target "tools-only" is better
than "HOST_TOOLS_ONLY=yes".
>
> Doesn't work for me:
> ========
> $ make tools-only
> HOSTCC scripts/basic/fixdep
> HOSTCC tools/aisimage.o
> HOSTCC tools/crc32.o
> HOSTCC tools/default_image.o
> HOSTCC tools/dumpimage.o
> In file included from include/version.h:11:0,
> from tools/dumpimage.c:11:
> include/timestamp.h:11:47: fatal error:
> generated/timestamp_autogenerated.h: No such file or directory
> #include "generated/timestamp_autogenerated.h"
> ^
> compilation terminated.
> make[1]: *** [tools/dumpimage.o] Error 1
> make: *** [tools-only] Error 2
> ========
Oops - My bad.
I was disabling timestamp.
Could you fix like this?
tools-only: scripts_basic $(version_h) $(timestamp_h)
$(Q)$(MAKE) $(build)=tools
It worked for me.
$ make tools-only
HOSTCC scripts/basic/fixdep
CHK include/config/uboot.release
UPD include/config/uboot.release
CHK include/generated/version_autogenerated.h
UPD include/generated/version_autogenerated.h
CHK include/generated/timestamp_autogenerated.h
UPD include/generated/timestamp_autogenerated.h
HOSTCC tools/aisimage.o
HOSTCC tools/crc32.o
HOSTCC tools/default_image.o
HOSTCC tools/dumpimage.o
HOSTCC tools/fdt.o
HOSTCC tools/fdt_ro.o
HOSTCC tools/fdt_rw.o
HOSTCC tools/fdt_strerror.o
HOSTCC tools/fdt_wip.o
HOSTCC tools/fit_image.o
HOSTCC tools/image-fit.o
HOSTCC tools/image-host.o
HOSTCC tools/image.o
HOSTCC tools/imagetool.o
HOSTCC tools/imximage.o
HOSTCC tools/kwbimage.o
HOSTCC tools/md5.o
HOSTCC tools/mkenvimage.o
HOSTCC tools/mkimage.o
HOSTCC tools/mxsimage.o
HOSTCC tools/omapimage.o
HOSTCC tools/os_support.o
HOSTCC tools/pblimage.o
HOSTCC tools/sha1.o
HOSTCC tools/ublimage.o
HOSTLD tools/mkenvimage
HOSTLD tools/dumpimage
HOSTLD tools/mkimage
HOSTCC tools/proftool
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-03-31 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 17:23 [U-Boot] [PATCH] kbuild/makefile: allow building host tools separately Alexey Brodkin
2014-03-28 6:36 ` Masahiro Yamada
2014-03-28 21:58 ` Alexey Brodkin
2014-03-31 1:43 ` Masahiro Yamada [this message]
2014-03-31 5:52 ` Alexey Brodkin
2014-03-31 6:43 ` Masahiro Yamada
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=20140331104335.DB68.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.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