Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS2022 Exporter #1704

Merged
merged 1 commit into from
Aug 31, 2021
Merged

VS2022 Exporter #1704

merged 1 commit into from
Aug 31, 2021

Conversation

nickclark2016
Copy link
Member

What does this PR do?

Adds VS2022 support for C++ projects. Closes #1674. Needs follow on for research and implementation of C# projects in VS2022.

How does this PR change Premake's behavior?

N/A

Anything else we should know?

Add any other context about your changes here.

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

Copy link
Member

@starkos starkos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@starkos starkos merged commit 07b4e9c into premake:master Aug 31, 2021
@Pirulax
Copy link

Pirulax commented Aug 31, 2021

Thank you very much for implementing it.
It was really annoying to retarget all the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Visual Studio 2022 support
3 participants