Bug #282
closed
rootfs rebuild takes too long when testing new toolchain builds
Added by Hammel over 10 years ago.
Updated over 10 years ago.
Description
When rev'ing the toolchain it needs to be tested against the kernel and rootfs. However, a full rootfs built with Buildroot can take many hours to rebuild (probably because it has far too much junk enabled in it, but that's for RM #232). I need a faster rootfs build to verify the toolchain.
The way to do this is to build Busybox alone, possibly with a stripped down applet list, and packaged as an ext3 image just like Buildroot is. This means copying over some of the buildroot targets like buildroot-ext3 and then testing ways to specify a custom config file for the stripped down version.
- % Done changed from 0 to 50
Add ability to make an ext3 image from the Busybox build and push it to the package directory as the rootfs.ext3 as a test rootfs. Also added ability to specify an alternative configuration (BC=) on the command line.
The build works but the resulting image hasn't been tested yet.
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
Updated Busybox build to allow building a minimal rootfs that will boot to a shell prompt. This is only useful for testing new toolchains since a full rootfs can take hours to complete while this rootfs takes about 90 seconds. The resulting rootfs.ext3 will replace the one in the package directory when busybox-pkg is run so you need to be careful to save off your previous Buildroot-generated rootfs is you need to save it.
rootfs was tested with current toolchain and kernel (3.10.y) and it boots fine. Now its ready to be tested with new toolchain builds.
Also available in: Atom
PDF
Updated by