mesonbuild/meson

Validate and warn about unknown systems and CPU families in cross files

Open

#3,751 opened on Jun 18, 2018

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Python (4,978 stars) (1,465 forks)batch import
crossenhancementgood first issuehelp wanted

Description

CPU family and system names are a "common contract" between build files from different projects, which is why we document them.

If people use an unknown system or cpu family in a cross file, we should warn and encourage them to report it to us so we can maintain a stable and known ABI for build files.

Contributor guide

Tech stack
python
Domain
build systemdevopstooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonMeson build system basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
This issue requests adding validation for unknown system and CPU family values in cross compilation files. The change likely involves modifying the cross file parser to check against a known list (documented in Reference tables.html) and emit a warning. Look for existing validation utility functions in the Meson source code, such as in 'mesonbuild/cross.py' or similar. Since there is an assignee, check for any linked branches or discussions to understand if work is already in progress.