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

fixed #12715 - made Visual Studio conditions work again #6404

Merged
merged 1 commit into from
May 21, 2024

Conversation

firewave
Copy link
Collaborator

No description provided.

@firewave
Copy link
Collaborator Author

firewave commented May 14, 2024

Backport for 2.14.x cherry-picked from #6389.

@firewave
Copy link
Collaborator Author

@danmar as this is a really bad regression we should really post official Windows binaries for 2.14.1 (well - we should always do that for the patches).

@danmar
Copy link
Owner

danmar commented May 21, 2024

@danmar as this is a really bad regression we should really post official Windows binaries for 2.14.1 (well - we should always do that for the patches).

OK. I guess I can try to release some official windows binary. I do plan to tag 2.14.1 soonish and release a new Cppcheck release based on that.

I don't usually make a full open source release if the changes are highly targeted to the premium handling.

@danmar danmar merged commit 4108369 into danmar:2.14.x May 21, 2024
63 checks passed
@firewave firewave deleted the vcproj branch May 21, 2024 19:07
@firewave
Copy link
Collaborator Author

I don't usually make a full open source release if the changes are highly targeted to the premium handling.

We (well, me) usually don't introduce regressions which completely break an important feature...

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