Hi Matt,
On 8 May 2017 at 10:38, Simon Glass sjg@chromium.org wrote:
Hi Matt,
On 1 May 2017 at 21:43, Matt Weber matthew.weber@rockwellcollins.com wrote:
Not all host systems want the default swig to be used when building the tools. Allow for the disabling of the wrapper to enable cross-compiling of the tools on a host system with swig.
Signed-off-by: Matthew Weber matthew.weber@rockwellcollins.com
I'm open for suggestions on what updates to make to enable the wrapper building to use prefix/destdir that point python/swig in the right place to the sysroot/host tools/libs for building of the tools.
Example build failure when buildroot is trying to build target/host uboot-tools and the host systems OS is detecting swig. The intention would be the buildroot built host python/swig should be used for the detect and as the tools assisting in the build. http://autobuild.buildroot.net/results/6d5/6d52ac8bb71012aea6fc4c679691b31a3...
tools/Makefile | 2 ++ 1 file changed, 2 insertions(+)
Can you please take a look at u-boot-fdt/next ?
That branch has the new approach for this feature. Can you try to get your path running on that branch and send v2?
This work is now in mainline. What do you think? Do you still need this patch?
Regards, Simon