Bug 14062 - Should we support native builds and ptest for all/most packages
Summary: Should we support native builds and ptest for all/most packages
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: oe-core other (show other bugs)
Version: 3.3
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Randy MacLeod
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-09-24 07:10 UTC by Randy MacLeod
Modified: 2026-06-19 20:26 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Randy MacLeod 2020-09-24 07:10:38 UTC
It might be nice to support building most packages natively and to be able to run ptests on these native packages. This would enable us to be able to easily compare the native ptest result with a cross-build result. Aside from inheriting native support, there may be a non-trivial amount of work so I'm just recording the idea here to see what others think.
Comment 1 Ross Burton 2020-09-24 08:19:11 UTC
Somewhere I had a branch that added a 'check' task between compile and install to let the recipe execute 'make check'.  I can't seem to find it though...
Comment 2 Randy MacLeod 2020-09-24 08:26:24 UTC
For some recipes such as udev or systemd this could be disruptive.
There are stll lots of recipes that do not even have ptests for the target and this more important than this enhancement.
Comment 3 Tim Orling 2024-10-03 15:02:39 UTC
Bump.
Comment 4 Randy MacLeod 2026-06-18 17:29:57 UTC
Ross, Tim, 
Should I close this enhancement as: resolved/obsolete
or can Ross find the WIP branch...
Comment 5 Ross Burton 2026-06-19 10:24:08 UTC
The branch is lost.

I do think it would be interesting to have opt-in testing for native recipes where 'make check' can work.  For select recipes only, I don't think we should be running the gtk4-native test suite because we can. But stuff like the autoconf and python where we're actively relying on them could be more interesting.
Comment 6 Randy MacLeod 2026-06-19 20:26:37 UTC
Thanks for the comment Ross - Low Future it is.