premake / premake/premake-core
How to deal with Visual Studio 2017 mid-release project format changes?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
So, we ran into the following issue.... Premake for Visual Studio 2017, while it works, if falling behind, because the amount of changes from VS 15.0.0 to VS 15.5.1 is quite large. More importantly, premake doesn't know which one it is targeting... we just say "vs2017", and I certainly wouldn't want to start making a new action for each new vs2017 release either...
but both toolchain, as well as the IDE has new settings, others have been removed, etc...
Anyone have a solid idea?
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
The issue names Visual Studio 2017 and differences between releases 15.0.0 and 15.5.1, but it identifies no files, tests, or entry point. Start by locating Premake's Visual Studio 2017 handling and version-selection logic, then define an approach that supports mid-release format changes without creating an action for every release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100