Yocto busybox menuconfig

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Yocto busybox menuconfig

39,846 Views
CurtisWald
NXP Employee
NXP Employee

In Yocto Project to access the busybox menuconfig system:

bitbake -c menuconfig busybox

bitbake busybox

bitbake fsl-image-fb

01. Execute the command menuconfig on the package busybox. This allows customization of busybox applets

02. Run all the tasks for package busybox

03. Create the final image, in this case the frame buffer image, see tmp/deploy/images for outputs.

-Curtis

Labels (2)
4 Replies

11,374 Views
MichaelBMiner
Contributor IV

Does Yocto use busybox by default? Is there more configuration to be done?

0 Kudos
Reply

16,253 Views
OtavioSalvador
Senior Contributor II

It's good to add it in a project specific layer and save it there with a busybox_<version>.bbappend instructing bitbake to check the layer's path for overrides. This allow for later reuse of the changed configuration and also store of it under a SCM system (as GIT, for example).

0 Kudos
Reply

16,254 Views
marcus123
Contributor I

Hi Otavio,

Could you elaborate on how this is best done with the Busybox Yocto build.

I am trying to enable 'init' within BusyBox which isn't enabled by the default configuration.

I have tried the following:

1. Run menuconfig  and enable 'init' configuration option.

     bitbake -c menuconfig busybox

2. Create a patch file for the of the changes to the '.config' file

     diff -Naur .config.old .config > busybox-enable-init-config.patch

3. Add the patch file to my custom board layer in the busybox.bbappend file and copy the patch file into the appropriate location.

     SRC_URI_append = " file://busybox-enable-init-config.patch"

This then fails to build:

ERROR: Command Error: exit status: 1  Output:

Applying patch busybox-enable-init-config.patch

can't find file to patch at input line 3

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--------------------------

|--- busybox-1.23.1/.config.old 2015-11-26 14:59:46.616876464 +1000

|+++ busybox-1.23.1/.config 2015-11-26 15:41:16.032997933 +1000

--------------------------

No file to patch.  Skipping patch.

This fails because the .config file doesn't exist at this stage of the build.

How should I apply my required changes to the Busybox configuration? Which file needs to be changed?

Regards

Marcus

16,254 Views
OtavioSalvador
Senior Contributor II

New Yocto Project releases allow the use of "config fragments" to change busybox settings.

You can add fragments and append them in SRC_URI. One example:

http://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git;a=blob;f=recipes-core/busybox/busybox_...