[DISPATCH-2027] Support the Windows OS

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.15.0
• Assignee: Jiri Daněk
• Reporter: Jiri Daněk
• Created: 30/Mar/21 20:55
• Updated: 16/Mar/22 09:15
• Resolved: 04/Jan/22 11:36

Description

Qpid Dispatch currently works only on Linux, macOS, and maybe SunOS and some *BSDs. We would like it to support the Windows OS too.

Previous discussions

1. Is there any Qpid Dispatch Router windows version?
2. [Qpid Dispatch] Runtime behavior on SunOS
3. [Qpid-dispatch] timespec not defined on Windows
4. https://twitter.com/ppatierno/status/792353537703419904

Sub-Tasks

• Replace usage of `clock_gettime` in `qd_timer_now` with `pn_proactor_now_64` from Proton: Closed
• Do not rely on long type being large enough to transfer C pointer values from C to Python: Closed
• Implement win32/threading.c: Closed
• Mark all functions called from Python with QD_EXPORT: Closed
• Use _aligned_malloc/_aligned_free on Windows; these _must_ be used in pair: Closed
• Get Dispatch to compile on Windows; CMakeLists.txt changes are needed: Closed
• tests\test_broker.py causes invalid operation under Windows: Closed
• Use setuptools instead of deprecated distutils: Open
• Dispatch confg refuses to load Windows paths with backslashes: Open
• system-tests configure connectors with host: 0.0.0.0; this works on Linux, but Windows needs to connect to 127.0.0.1: Open