Bug 15854 - Meson cannot be used in minimal eSDK
Summary: Meson cannot be used in minimal eSDK
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 5.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.2
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2025-05-06 19:05 UTC by Ross Burton
Modified: 2026-10-27 11:01 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2025-05-06 19:05:27 UTC 
Meson has a post-relocate-setup.d script to generate the correct cross files at configuration time in eSDKs.

However, a minimal eSDK isn't able to run those when the recipe is installed with 'devtool sdk-install'.

Either we need to rewrite meson's recipe to not need this stage (not sure how to do this), or sdk-install should run new post-relocate scripts.
Comment 1 Randy MacLeod 2025-05-08 14:46:32 UTC 
Ross is going to skip this is the test.
Perhaps warn if meson is added to eSDK after generation.
Comment 2 Richard Purdie 2026-08-21 22:27:41 UTC 
Something isn't right here. eSDK would use meson-native just the same as a normal build would, so shouln't this "just work"?

I notice meson-native does install meson-setup.py into datadir, but where is it actually run, if ever?