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
Windows build for nghttp2 supported? #184
Comments
They're all official but yeah at some point we will reduce the number of options. The nmake versions in the root dir is probably the one most likely to get ditched first. Otherwise we're a bit short on people working on windows and I'm not sure anyone has built http2 support with MSVC previously. Feel free to use your own preferred method and add http2 support to it! |
ok, thanks for this explanation. |
Hmm sad, it's still not possible to build curl with nghttp2 on windows. |
It is still very much possible as lots of people already do it since a long time back. I assume you're talking about lack of support in some specific build files? If so, we do welcome patches and help to fix remaining problems. |
sorry, I meant out of the box. Cmake warns to be poorly maintained and failed in configuring So what is the preferred way to compile curl with http2 using MSVC? |
cmake support for nghttp2 builds is discussed in #922 I think most people who build curl with nghttp2 on windows use msys/mingw, but I'm not sure. I'm not on windows myself. So again: it works for some build setups, just not all. And possibly not the one you want to use. |
OK thanks, Curl is not my main focus so I can't invest lots of time to integrate http2 support in windows. So I will ship curl with http 1 support only. Anyway: Good work and very clean project structure when buijlding curl form sources. Great job! |
I've tried to build curl with nghttp2 on windows x64:
nghttp2/nghttp2#195
Currently, it's not really possible to build CURL with nghttp2 support without build modifications?
And I don't know what are the "official" way to build CURL for windows:
?
Thanks
The text was updated successfully, but these errors were encountered: