On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via lists.openembedded.org wrote: > On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund > <joakim.tjernl...@infinera.com> wrote: > > I will try workaround these somehow but will not go so far as creating a > > new MACHINE just to > > run these tests. > > Why would you need a new machine? You only need a new configuration > template in addition to existing one (e.g. > conf/templates/repro-test/local.conf.sample and bblayer.conf.sample). > Then initialize the build with TEMPLATECONF pointing to that.
Ah, there is an idea. But this will still change the original machine so one cannot switch between normal builds and repro builds in he same tree. > > > But now you know what the main issue is, hopefully you can fix these > > somehow. > > Why not force offending config off instead of error out(in kirkstone too > > please)? > > Patches from you would be most welcome. I think there's a already a > mechanism where build-st/conf/ contains a custom local.conf, so all > the needed settings could be added at the point where that is created? Yes, I think so. My python skills are pretty non existent though. > > Alex > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#194370): https://lists.openembedded.org/g/openembedded-core/message/194370 Mute This Topic: https://lists.openembedded.org/mt/103973969/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
