On Mon, 3 Jun 2024 at 11:40, Fabio Berton via lists.openembedded.org <[email protected]> wrote: > Based on this, I would say that we don't want to build tests unless ptests > are enabled (so the argument that building tests also tests the code is > moot). In turn, it may be sensible to use the default CMake option to disable > building of tests.
It's actually more subtle. If a recipe has ptest support, then it can use that to enable/disable building of tests. If a recipe has no ptest support, then there's not global rule on what to do. Some recipes disable them, others simply keep things at default settings. I wouldn't want to change a global default for all cmake recipes unless there is compelling reason, because users may be relying on that default, and it will break things for them needlessly. The correct thing to do, if you observe tests that are being built but are not being run, is to add ptest support to the recipe. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#200243): https://lists.openembedded.org/g/openembedded-core/message/200243 Mute This Topic: https://lists.openembedded.org/mt/105688417/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
