Ok guys, I gave up for now. Maybe I will try to fix it in the future, or somebody else can do that ...
Cheers, Andrej >> This option allows correctly handle the release/debug flags separation >> in upper recipe like cmake. Adopt SELECTED_OPTIMIZATION usage in other >> recipes. >> >> Signed-off-by: Andrej Valek <[email protected]> >> Signed-off-by: Pascal Bach <[email protected]> >> Signed-off-by: Adrian Freihofer <[email protected]> >> --- >> meta/conf/bitbake.conf | 7 ++++--- >> meta/conf/distro/include/security_flags.inc | 8 ++++---- >> meta/conf/local.conf.sample.extended | 1 + >> meta/recipes-devtools/valgrind/valgrind_3.16.1.bb | 1 + >> 4 files changed, 10 insertions(+), 7 deletions(-) > > I am a bit worried about this as we're effectively letting cmake's idea of > flags separation determine how we have to set > things in OE. Once we go down > this route, we're going to have problems any time we try and add a new > compiler flag. > > What does this buy us in the end? > > Cheers, > > Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#144985): https://lists.openembedded.org/g/openembedded-core/message/144985 Mute This Topic: https://lists.openembedded.org/mt/78460656/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
