mesonbuild/meson

Allow debugging internal commands

Open

#2,900 opened on Jan 8, 2018

View on GitHub
 (0 comments) (4 reactions) (0 assignees)Python (4,978 stars) (1,465 forks)batch import
enhancementgnomegood first issuehelp wanted

Description

gnome.gtkdoc() is indirectly called through meson --internal gtkdoc. That means two things:

  • We can't call ninja some_file_generated_by_gtkdoc-mkdb (it's called by meson --instal...)
  • We can't see the "real" command (gtkdoc-mkdb) to check the passed arguments. That'd be great to have a --verbose parameter to pass to meson and meson --internal. Meson also should print the commands on fail (just as Ninja does). Another way to solve the problem would be to completely remove the --internal calls and let ninja do the job.

Contributor guide

Tech stack
python
Domain
build systemdeveloper experiencecli
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonMeson build system internalscommand line argument parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how `meson internal` commands are implemented, likely in `mesonbuild/meson.py` or related modules. Add a ` verbose` flag to the `meson` command that propagates to internal command dispatchers. For example, modify the ` run internal command` function to accept and forward verbose flag. Ensure that the actual commands executed are printed to stderr or stdout. Test with a sample project using gtkdoc.