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

Query on go-forward plan for the Windows build #635

Closed
SLDiggie opened this issue Apr 12, 2022 · 2 comments
Closed

Query on go-forward plan for the Windows build #635

SLDiggie opened this issue Apr 12, 2022 · 2 comments

Comments

@SLDiggie
Copy link

I am looking to move to 1.2.12 as a result of CVE-2018-25032, but stymied by some issues in the Windows builds.

Things like:

And then there are some indirect issues that just look a bit concerning, like #623.

I can see madler has made a few commits on the develop branch, last commit 13 days ago at the time of writing. There are also some suggestions for workarounds for some of the issues, but it's not easy to tell whether they are actually the right thing to do or if they just silence an error and could raise other problems.

As the CVE is rated high severity there is a sense of urgency to upgrade, but I would prefer to move to an official tag from madler rather than 1.2.12 with cherry picks from develop or workarounds from this issue tracker thrown over the top. For planning purposes, is there a 1.2.13 tag coming soon, or else what is the official recommendation for vstudio-based consumers?

@madler

@nmoinvaz
Copy link
Contributor

You can use cmake to generate the visual studio projects and solutions.

@madler
Copy link
Owner

madler commented Oct 6, 2022

Closing, as this refers to other existing issues.

@madler madler closed this as completed Oct 6, 2022
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

No branches or pull requests

3 participants