On Mon, 2014-07-28 at 22:22 +0200, Jeroen Hofstee wrote: > Hello Ian, > > On 28-07-14 21:29, Ian Campbell wrote: > > This tool is potentially useful on host systems. In particular I'd like to > > make > > use of it at build time from the sunxi-tools package in Debian. > No this does not make sense. Why should a MAKEALL for powerpc > build mksunxiboot hundreds of times, while it not using it, while you > ship a arch specific package in Debian?
Hrm, I incorrectly thought that hostprogs-y covered more stuff but I was wrong. > Can't you just put this under HOST_TOOLS_ALL and ship an > u-boot-tools package or something? The problem with HOST_TOOLS_ALL is that it requires a configured tree. At the moment we have tools-only which does not require a configured tree but only includes a minimal set of tools and tools-all (HOST_TOOLS_ALL) which does require a configured tree but in addition to the tools which the config implies also builds all "config-independent" tools as well. Debian currently builds tools-only into a u-boot-tools package and the various target specific files into another package. I'd like to get mksunxiboot into the u-boot-tools package (or perhaps u-boot-tools-sunxi) so it is available even on non-sunxi (or even non-ARM) systems. Perhaps what is needed is a third target between tools-only and tools-all which builds all config-independent tools without requiring a config? e.g. tools-all-only? Or maybe it would be possible to relax tools-all such that it doesn't require a configured tree. Any opinions on those two options? FWIW the first option would end up looking something like below, I've not prototyped the second one yet. Ian. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
