mesonbuild/meson

compiler.run() current working directory and cleanup

Open

#2,519 opened on Oct 22, 2017

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

Description

I need to run code that writes files in compiler.run(). Turns out the current working directory is the same as for the meson (or ninja) invocation. If I don't manually clean up the generated files in the code being run, they're left behind.

I'd like to be able to pass the workdir to compiler.run() not unlike test() workdir, and/or have the code executed in a temporary directory that's automatically discarded afterwards. Having to do this yourself in a C or C++ code snippet is tedious at best.

Contributor guide

Tech stack
python
Domain
build system
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.
half day
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
Understanding of Meson's compiler.run() functionPython skills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the implementation of compiler.run() in Meson, likely in mesonbuild/compilers/compilers.py. The goal is to add a workdir parameter or automatic temporary directory cleanup. Review the existing test() workdir mechanism for reference. Ensure backward compatibility.