Ran
|
Jobs
1
|
Files
232
|
Run time
14s
|
Badge
README BADGES
|
travis-ci
<a href="https://github.com/zeromq/libzmq/commit/<a class=hub.com/zeromq/libzmq/commit/d78feed7a109d9f8c9f047f57992e2eaae7431f4">d78feed7a<a href="https://github.com/zeromq/libzmq/commit/d78feed7a109d9f8c9f047f57992e2eaae7431f4">">Fixes for Windows XP compatibility A Visual Studio build from master (commit id: </a><a class="double-link" href="https://github.com/zeromq/libzmq/commit/<a class="double-link" href="https://github.com/zeromq/libzmq/commit/dac5b45dfb224ff184a7aed39c5859ae5bac3803">dac5b45df</a>">dac5b45df</a><a href="https://github.com/zeromq/libzmq/commit/d78feed7a109d9f8c9f047f57992e2eaae7431f4">) using the v140_xp toolset yields a binary that is not XP compatible. Two libraries contain exports that cannot be found: - IPHLPAPI.DLL : if_nametoindex - KERNEL32.DLL : InitializeConditionVariable The latter export is already dealt with in the file './src/condition_variable.hpp'; however this requires setting the _WIN32_WINNT pre-processor definition. I am not experienced enough to figure a work around for the 'if_nametoindex' method, so I have created a new pre-processor definition 'ZMQ_HAVE_WINDOWS_TARGET_XP' and removed the calling of the function with the limitation that these builds cannot handle a IPv6 address with an adapter name. To make it easier for people targeting XP with an MSVC build I have modified the MSBuild property file to add/modify the pre-processor definitions if they are building using a XP targeting tool set; such as v140_xp.
7968 of 10703 relevant lines covered (74.45%)
36345.85 hits per line
Lines | Coverage | ∆ | File |
---|---|---|---|
1 |
54.83 |
0.0% | src/tcp_address.cpp |
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
6 | 2010.6 (BUILD_TYPE=coverage CURVE=tweetnacl) | 232 |
74.45 |
Travis Job 2010.6 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|