Skip to content

Integrate seco-base/custom_support

GitBot requested to merge integrate/seco-base/custom_support/into/kirkstone/develop into kirkstone/develop

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/3674433cf349ba76c909ded7cc0500ab3d8b3581

[YCONFIG] Fix Yconfig_hw_configuration

Point to the right Yconfig file inside the custom meta layer.

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/9735ae8f6ae683d35f689c9f869fac94c34f7dcc

Fix Typo

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/a1a828471ca9b49dc7bee5e0d63a319dc25283b0

Add defconfig for Edgehog Embedded usage

Created defconfigs with Edgehog Embedded for all supported boards.

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/555e8b3025de5ea3d62a7c162811d1c28644d357

[MENUCONFIG][TOOL] Update mconf/conf with osource keyword

ref: https://git.seco.com/yocto_ng/tools/menuconfig/-/commit/4ecee598f9a7d1091253a71b1e1aade43572f69b

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/0bd2138b26d7375f2e249a92d17454bf335ec948

[MENUCONFIG][ENVIRONMENT] Add Edgehog Embedded environment

Add environment for Seco distro for embeedded devices, without any IoT feature

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/d2adc1f96ff36bd3673fb294097f195c1d28ae1a

[CONFIGURATOR] Fix error in python script

May append that the follow CONFIG_ item are empty string: astarte_url astarte_realm astarte_pairing_token

This causes the following error:

conf_string += ":" + "astarte_realm=" + astarte_realm

Fix with checking that those variables are not None.

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/628270f28b9cdff8cbc9c455ec9888f3c0d55f1b

[CONFIGURATOR] Add support for an optional custom layer

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: https://git.seco.com/yocto_ng/tools/menuconfig/-/commit/4ecee598f9a7d1091253a71b1e1aade43572f69b 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