The change [1] should fix the windows behavior (after
inspecting an obviously
different version of sdkddkver.h, but i can't spot anything
else looking suspicious).
Does anyone know, why we have a define for _WIN32_WINNT in
our sources?
Windows should know, what version it has. Maybe a leftover?
Andrew, can you check, what happens, if we remove it?
-g
[1]
https://bitbucket.org/naviserver/naviserver/commits/b743a8847dd01704ffdcfe98cc8a95a80ad7eea1
[2]
http://sourceforge.net/p/mingw/mingw-org-wsl/ci/9313d16b81162e4d6f58aa5b4a08d16dbcbccdb6/tree/include/sdkddkver.h
On 26.09.14 04:59, Andrew Piskorski wrote:
Uh oh, Gustaf, I just merged your recent changes into my fork, and now
when I try to compile anything, it immediately fails with:
C:\Program Files\Microsoft SDKs\Windows\v7.1\INCLUDE\sdkddkver.h(246) :
fatal error C1012: unmatched parenthesis : missing ')'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\Bin\amd64\cl.EXE"' : return code '0x2'
Stop.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
