| Summary: | Should we support native builds and ptest for all/most packages | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Randy MacLeod <randy.macleod> |
| Component: | oe-core other | Assignee: | Randy MacLeod <randy.macleod> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | ross.burton, tim.orling |
| Version: | 3.3 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Randy MacLeod
2020-09-24 07:10:38 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... 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. Bump. Ross, Tim, Should I close this enhancement as: resolved/obsolete or can Ross find the WIP branch... 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. Thanks for the comment Ross - Low Future it is. |