Deprecate and Remove [target_machine] from cross file format
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
Meson does nothing itself with the target machine. I think its a bit misleading that it parses it at all when only user-written logic can use it. I've talked in #3972 about having separate host and target files rather than just one cross file. I think it would be best to:
- Remove
[target_machine] - Rename
[host_machine]to[machine] - Add
[machine]to native platform for consistency. - Use a separate target file if we ever wish to support target platforms "for real"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the cross file format and native platform handling, then read the discussion in issue #3972 for the context on separate host and target files. Done means removing [target_machine], renaming [host_machine] to [machine], and adding [machine] to the native platform while preserving the proposed future target-file direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100