Commit 9409c9bd authored by Martin Storsjö's avatar Martin Storsjö

configure: Disable networking if winsock2.h is available but winsock functions aren't

Previously, if neither of the checks for the closesocket function
succeeded, we still kept winsock2.h and networking in general
enabled.

When targeting the WinRT API subset, the winsock2.h header is
available (making the check for it succeed, giving the impression
that winsock is available), but tests that actually try to use
such a function will fail. In this case, disable the winsock2.h
feature and networking in general, as if the winsock2.h header
test would have failed in the first place.
Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
parent 01d245ef
...@@ -3776,7 +3776,7 @@ if ! disabled network; then ...@@ -3776,7 +3776,7 @@ if ! disabled network; then
check_func_headers winsock2.h closesocket -lws2 && check_func_headers winsock2.h closesocket -lws2 &&
network_extralibs="-lws2" || network_extralibs="-lws2" ||
{ check_func_headers winsock2.h closesocket -lws2_32 && { check_func_headers winsock2.h closesocket -lws2_32 &&
network_extralibs="-lws2_32"; } network_extralibs="-lws2_32"; } || disable winsock2_h network
check_func_headers ws2tcpip.h getaddrinfo $network_extralibs check_func_headers ws2tcpip.h getaddrinfo $network_extralibs
check_type ws2tcpip.h socklen_t check_type ws2tcpip.h socklen_t
check_type ws2tcpip.h "struct addrinfo" check_type ws2tcpip.h "struct addrinfo"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment