mesonbuild/meson

Add a mechanism to add prefix/suffixes to configuration files

Open

#1,492 opened on Mar 22, 2017

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Python (1,465 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (4,978 stars)
PR merge metrics
 (Avg merge 139d 13h) (51 merged PRs in 30d)

Description

Right now, with configure_file() if the input: kwarg is not set, we just dump the entire configuration. This has the advantage of not having to maintain a duplicate list of defines (one in meson.build, another in config.h.in) and is less error-prone.

However, this leaves a gap: sometimes the config.h is mostly generated, but has a few static defines in it. We should implement a way to also add these to the generated config.h. There are two ways to implement this:

  1. Add prefix: and suffix: kwargs to configure_file()

  2. Add a new token type #meson_dump_configuration (or similar) that can be put in config.h.meson that will dump the configuration_data() object in that place

The latter has the advantage of being more flexible, and the former has the advantage of having all the defines in one place (in meson.build).

Contributor guide

Research direction
Evaluate the two proposed implementations for adding prefix/suffix to configuration files: 1) adding `prefix:` and `suffix:` kwargs to `configure file()`, or 2) adding a new token type `#meson dump configuration` that can be inserted into config files. Determine which approach is more flexible and less invasive, then implement the chosen approach in the Meson source code.
Tech stack
python
Domain
build systemtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75