-
Notifications
You must be signed in to change notification settings - Fork 34
Fix warnings in server.c / client.c Windows build #235
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
Comments
jsha
pushed a commit
that referenced
this issue
Apr 13, 2022
This adds a cross-platform CMake build system, which supports basic building and testing on Linux, macOS and Windows. (It does not yet have parity on Linux/macOS debug builds, sanitizer builds, or running test harnesses, but those could be added in the future with CMAKE_BUILD_TYPE conditionals and CTest. It also doesn't cover the install step yet.) I also rewrote the bash test harnesses in Python, as a cross-platform substitute, and fixed a couple portability issues with the test programs. * Added CMake projects. * Added Python versions of shell scripts. * Moved Windows compatibility defines to common.h, so common.c would see them. (Prior to this, read_cb was checking `errno` rather than `WSAGetLastError()`, failing to properly handle `WSAEWOULDBLOCK`, and reporting an EOF too early. * Added a forward declaration of `ws_strerror()`. Without this declaration, the compiler would assume it returned an `int` rather than a pointer, which resulted in the pointer getting truncated, and a later `fprintf` call performing a wild read. (In retrospect, this was foretold in #235) * Added CMake CI jobs on Windows, macOS, and Linux. Fixes #192, fixes #121
Merged
jsha
pushed a commit
that referenced
this issue
Dec 11, 2022
I think the contributions in #275 did the hard work here. I'm only seeing two warnings in the CMake windows builds as of the time of writing:
I think #405 will fix both and resolve this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: