Visual Studio project backend OutDir option
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 1.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
Possibly related to Enhancement Request https://github.com/mesonbuild/meson/issues/429:
In order to structure the generated VS backend into separate directories for its source project files and corresponding build directory, there should be an option to set the project files' OutDir variable.
I am thinking of a similar mechanism as is being implemented for setting the startup project: https://github.com/mesonbuild/meson/blob/619e05c8cf889c84fc619a54e8f8dddba228bd0a/mesonbuild/backend/vs2010backend.py#L404
I'd offer to try myself at implementing this, if there are no specific reasons that speak against it.
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 with mesonbuild/backend/vs2010backend.py around the startup-project handling referenced in the issue, then trace how Visual Studio backend options are defined. Done means the backend supports configuring the project files' OutDir so generated project files and their corresponding build directory can be placed separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100