-
Johannes Kanig authored
The windows version of why3server (and client) now also handles a path as socket name. However, on windows sockets are not paths, so it just throws away the path part of the socket name, and just uses the basename. Change-Id: I11d5c0f1023cb21eb105a892f12065d918b9eb9c (cherry picked from commit 924dbfe1f52c9197939d763fb72df9b980efd511)
2aeae0f1