summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2017-10-17 13:42:44 +0900
committerTom Rini <trini@konsulko.com>2017-11-17 07:43:32 -0500
commitd6a0c78a4efb1353f4ec6f6c59c0771298510f58 (patch)
treef182d9931b330fa498c6f42da989e0593aa134ff /include
parent15b97f5c5e6d88e0560c6928f3acd01c999a494d (diff)
downloadu-boot-d6a0c78a4efb1353f4ec6f6c59c0771298510f58.tar.gz
u-boot-d6a0c78a4efb1353f4ec6f6c59c0771298510f58.tar.bz2
u-boot-d6a0c78a4efb1353f4ec6f6c59c0771298510f58.zip
pylibfdt: compile pylibfdt only when dtoc/binman is necessary
Currently, pylibfdt is always compiled if swig is installed on your machine. It is really annoying because most of targets (excepts x86, sunxi, rockchip) do not use dtoc or binman. "checkbinman" and "checkdtoc" are wrong. It is odd that the final build stage checks if we have built necessary tools. If your platform depends on dtoc/binman, you must be able to build pylibfdt. If swig is not installed, it should fail immediately. I added PYLIBFDT, DTOC, BINMAN entries to Kconfig. They should be property select:ed by platforms that need them. Kbuild will descend into scripts/dtc/pylibfdt/ only when CONFIG_PYLIBFDT is enabled. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions