premake / premake/premake-core
Clean does not delete outputs produced by custom rule in Visual Studio
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
What seems to be the problem?
Basically what the title says.
What did you expect to happen?
I expected the clean button to delete all compiled outputs, including ones generated by a custom rule.
How can we reproduce this?
Create a premake file with a project that uses a custom rule that generates outputs. Then compile the project (which should generate the outputs) and then clean it. Open the binary folder and you would see the outputs are still there.
- Visual Studio 2022 (vs2022)
- Visual Studio 2019 (vs2019)
- Visual Studio 2017 (vs2017)
- Visual Studio 2015 (vs2015)
- Visual Studio 2012 (vs2012)
- Visual Studio 2010 (vs2010)
- Visual Studio 2008 (vs2008)
- Visual Studio 2005 (vs2005)
- GNU Makefile (gmake)
- GNU Makefile 2 (gmake2)
- XCode (xcode)
- Codelite
- Other (Please list below)
What version of Premake are you using?
premake5 (Premake Build Script Generator) 5.0.0-beta2
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
Reproduce the issue with a premake file containing a custom rule, using Visual Studio 2022, then compile and clean the project. Inspect the generated binary folder to identify why custom-rule outputs remain. Done means the clean operation removes those outputs as well as the other compiled outputs.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100