mesonbuild/meson

compiler.run() current working directory and cleanup

Open

#2,519 opened on Oct 22, 2017

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

Repository metrics

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

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

Research direction
Examine the implementation of test() workdir parameter and temporary directory cleanup. Adapt compiler.run() to accept an optional workdir argument and clean up temporary files when done.
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.
1-3 hours
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.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70