EBC Exercise 27 BusyBox

We'll attack getting BusyBox like we did getting the kernel (ECE597 Configuring the Kernel) though the paths will be slightly different. Make sure you have commented out in the local.conf file. See ECE597 Configuring the Kernel for details.
 * 1) INHERIT += " rm_work "

Check and see what you already have for previous installations: cd ${OETREE}/angstrom-dev/work/beagleboard-angstrom-linux-gnueabi ls Do you see BusyBox? I didn't. Do this to find it: cd ${OETREE}/angstrom-dev/work find. -name "*busybox*" The  command will find all files and directories that contain the name. BusyBox is not a Beagle specific compile, so it appears in a different location. Change to the BusyBox directory and look around. Can you find the source? If not, try cd ${OETREE}/openembedded $ bitbake -c clean busybox $ bitbake -f -c compile busybox This took just a few minutes on my machine. Your mileage may vary. Once done look again for the BusyBox sources. Hint: they aren't in a git directory.

You can now configure BusyBox. make xconfig After saving the configuration changes to update the .config file, it is a simple matter of running make. $ make