Skip to contentSkip to conversation

cml1.bbclass: Return sorted list of cfg files

DISCUSSION Volker Vogelhuber 2 participants 2 messages May 17, 2021

lore
Share & tools
lore
#0 lore raw

The commit dee41e92f0efac7e453597bed4b4c02f867e3aa9 has introduced a behavior change when adding different cfg files configuring the same configs.

So e.g. when configuring busybox, the default recipe adds a syslog.cfg which enables CONFIG_SYSLOGD=y.
So far we had a .bbappend file that adds another .cfg file "disable_syslog.cfg" that changes this to "# CONFIG_SYSLOGD is not set".

As the SRC_URI files are now sorted alphabetically, this results in the disable_syslog.cfg being passed to merge_config.sh before syslog.cfg which in the end is not what we intended. We solved it now by doing a SRC_URI_remove in the bbappend, but I'm not sure, if that sorting is causing side effects in other places as well.

#1 lore raw
Quoted 8 lines · Volker Vogelhuber

The commit dee41e92f0efac7e453597bed4b4c02f867e3aa9 has introduced a behavior change when adding different cfg files configuring the same configs.

So e.g. when configuring busybox, the default recipe adds a syslog.cfg which enables CONFIG_SYSLOGD=y. So far we had a .bbappend file that adds another .cfg file "disable_syslog.cfg" that changes this to "#CONFIG_SYSLOGD is not set".

Quoted 5 lines

As the SRC_URI files are now sorted alphabetically, this results in the disable_syslog.cfg being passed to merge_config.sh before syslog.cfg which in the end is not what we intended.
We solved it now by doing a SRC_URI_remove in the bbappend, but I'm not sure, if that sorting is causing side effects in other places as well.

I think the issue was elsewhere and we should revert this change.

Cheers,

Richard