On Thu, Jan 22, 2015 at 11:11 AM, Raphael Philipe <rapp...@gmail.com> wrote: > Thank you Wolfgang, > > For the especific case of the env tool, One can build it to run on the > host to produce a environment variables binary file for the target > (This can be used while building some image to be written in a sd > card, spi flash or the like). For this specific case I'm in doubt on > how to compile it. I'm trying to compile it for beaglebone black. > > I was able to compile it, but I'm not sure if I did it properly. > Moreover I would like to know the role of HOSTCC in it and if it is > correct to access it directly. > > I used the following commands: > > make am335x_evm_config CROSS_COMPILE=arm-poky-linux-gnueabi- > HOSTCC="gcc " CC="arm-poky-linux-gnueabi-gcc -march=armv7-a > -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 " > make env CROSS_COMPILE=arm-poky-linux-gnueabi- HOSTCC="gcc " > CC="arm-poky-linux-gnueabi-gcc -march=armv7-a -mfloat-abi=hard > -mfpu=neon -mtune=cortex-a8 " > > Using this approach, I can compile code for the host that is dependent > on the target architecture. > > All of this makes sense?
It does as the env tools rely on the target setup (environment size, offset, ...) to do its job. So it does make sense. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
