On Friday 06 February 2009 14:59:10 Peter Tyser wrote: > On Fri, 2009-02-06 at 20:06 +0100, Wolfgang Denk wrote: > > In message Peter Tyser wrote: > > > Add a mkimage_win32.exe build target which can produce a native > > > win32 mkimage executable using the MinGW toolchain. The > > > mkimage_win32.exe binary is generated when the MINGW_COMPILE > > > environment variable is defined. The mkimage_win32.exe binary > > > can be used by those who use Windows as an OS build environment > > > but don't use cygwin. > > > > Why do we need a new envrironment variable? Can we not follow the > > standard pattern ansd use CROSS_COMPILE instead? > > Most files can't be compiled with MinGW so if CROSS_COMPILE is set to a > MinGW compile errors quickly occur in the build process. Also, it would > be a bigger pain to compile u-boot + mkimage_win32.exe. Eg: > > export CROSS_COMPILE=powerpc-linux- > export MINGW_COMPILE=i586-mingw32msvc- > make > > vs > > export CROSS_COMPILE=i586-mingw32msvc- > make > cp tools/mkimage_win32.exe ~/ > make clean > export CROSS_COMPILE=powerpc-linux- > make
i think you're trying too hard. you're trying to combine three targets at once: the host system (ppc), the build system (i686 prob), and canadian cross for some other random build system (mingw). the logical step would be to only build the tools for your random other build system instead of trying to combine it all together. in other words, set the HOSTCC to your mingw compiler and only process the tools target. this is how every other package out there works and it doesnt really make sense to have u- boot be different in this regard. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
