Skip to content

[CONFIGURATOR] Add support for an optional custom layer

Davide Cardillo requested to merge custom_support into kirkstone/develop

Introduced the possibility to dynamically add an external (custom) layer inside the configurator tool.

Motivation: sometimes we have the need to add an external layer (for example a layer for a customer) without modifying the content of base folder (so without apport changes to this repo). So there is the need to dynamically add this additional layer in order to:

  • from seco-setup.sh script, check the condition for which an external layer has to be introduced.

  • inside the menuconfig, add all Yconfig files present in this external layer

  • add all defconfig file present in this external layer

  • add all bblayer listened inside the bblayer file presents in this external layer

  • menuconfig: use of the custom osource Kconfig's keyword. This allows us to introduce new optional configuration files. With the usage of osource entry, if no any custom layer is added, the tool conitues to work normally. ref: yocto_ng/tools/menuconfig@4ecee598 To tell to menuconfig (mconf/conf) tool to consider an extra layer, the CUSTOM, populated with the name of the layer to add (without meta-) environment variable has to be passed:

    ex: CUSTOM=seco-custom mconf [...]

      To add meta-seco-custom layer to the others.

  • The only thing to do in order to add this external layer is to create a file (in the root folder of the yocto project (so at the same level of layers folder) the file

    custom_layer

with inside the name of the layer to add (without meta- prefix).

Merge request reports