On Fri, Dec 08, 2017 at 04:16:41PM -0800, Sergey Kubushyn wrote:
On Fri, 8 Dec 2017, Simon Glass wrote:
Hi Stephen,
On 8 December 2017 at 16:28, Stephen Warren swarren@wwwdotorg.org wrote:
Simon,
Is it expected that the latest u-boot-dm.git master branch now requires swig? All the non-sandbox builds on my test systems are failing:
CHK include/config/uboot.release CHK include/generated/timestamp_autogenerated.h GEN ./Makefile UPD include/generated/timestamp_autogenerated.h CHK include/config.h CFG u-boot.cfg SHIPPED scripts/dtc/pylibfdt/libfdt.i PYMOD scripts/dtc/pylibfdt/_libfdt.so unable to execute 'swig': No such file or directory error: command 'swig' failed with exit status 1 make[4]: *** [scripts/dtc/pylibfdt/_libfdt.so] Error 1 make[3]: *** [scripts/dtc/pylibfdt] Error 2 make[2]: *** [scripts/dtc] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs....
Yes, unless we have a very recent libfdt on the system (and even then I'm not sure that it is picked up). We need swig to build pylibfdt which is needed for binman.
Err, would it be long before we need Java/Eclipse/Maven/younameit to just build U-Boot?
There is a fine line to be walked here. On the flip side, do we want to have to depend on N little external tools to put together a functional image? We can use binman to avoid some subset of that. That said, Simon, are we only building binman related stuff when we need binman in the end? Thanks!