Le dimanche 19 juillet 2015 à 17:47 +0200, Holger Levsen a écrit :
There seem to be two solutions to this:
- Including a script (e.g. the one from coreboot) to build the toolchain
as part of the build process
- Using native builds with visualization on the servers that run the
builds for the reproducible task force
I tend to prefer the second one since it only requires a one-time setup cost, while the other one, that requires to build toolchains for each test build, implies a considerably longer build time for each test.
these hosts also need maintenance so I actually prefer the first.
I understand. We could raise the topic on the U-Boot mailing list and see whether adding the scripts to build the cross-compilers tu U-Boot would be doable or not.
Otherwise, we can just grab those scripts aside the U-Boot source code for the reproducible task, so that we don't have to wait for a long discussion to conclude.
The basics for building U-Boot are the following (e.g. for the Cubieboard2 target) git clone git://git.denx.de/u-boot.git cd u-boot make -C $SRC O=$DST CROSS_COMPILE=$CROSS_COMPILE Cubieboard2_defconfig make -C $SRC O=$DST CROSS_COMPILE=$CROSS_COMPILE
aint there a makefile with a proper target? Also how to build these cross compilers?
I am using those scripts, that I wrote: http://git.paulk.fr/gitweb/?p=embedded-freedom-scripts.git;a=tree;f=u-boot;h...
That can help but is not really usable as-is.
Let me know if you need more indications on this.
yes, please. best a complete runnable script, aka a _working_ 5-10 liner, not the fancy one with variations, rebuilds and running debbindiff. Just the above "4 lines in working" - (those 4 lines dont work cause the variables are not defined...)
I could do that, but we have to figure out the toolchain issue first, I suppose.