On Fri, 17 May 2013, Jean-Baptiste Kempf wrote:
On 17 May, Martin Storsjö wrote :
I also amended the default version to 0x0501 (which is XP, while
0x0502 is Windows Server 2003).
XP is not supported anymore. Only XP SP2 is.
Windows Server 2003 is 0x501, since it is the same kernel as XP.
Wi
On 17 May, Martin Storsjö wrote :
> I also amended the default version to 0x0501 (which is XP, while
> 0x0502 is Windows Server 2003).
XP is not supported anymore. Only XP SP2 is.
Windows Server 2003 is 0x501, since it is the same kernel as XP.
Windows XP SP2 and Windows Server 2003 SP1 are 0x50
On Fri, 17 May 2013, Diego Biurrun wrote:
On 05/17/2013 04:20 PM, Martin Storsjö wrote:
MSVC 2010 (or more precisely, Windows SDK 7.0 which comes with MSVC
2010) sets _WIN32_WINNT to the constant for Windows 7 if nothing is
set. This could lead to the libav configure script detecting and
using
On 17 May, Diego Biurrun wrote :
> For example, I can never remember which _WIN32_WINNT
> version corresponds to which Windows release.
But it's obviously "simple"!
Win2000 is 0x0500
Win XP is 0x0501
Win XP SP2 is 0x502 (it's just a service pack!)
Vista is 0x600
7 is 0x0601 (of course!)
8 is 0x0
On 05/17/2013 04:20 PM, Martin Storsjö wrote:
MSVC 2010 (or more precisely, Windows SDK 7.0 which comes with MSVC
2010) sets _WIN32_WINNT to the constant for Windows 7 if nothing is
set. This could lead to the libav configure script detecting and
using functions only present in Windows 7 or newer
MSVC 2010 (or more precisely, Windows SDK 7.0 which comes with MSVC
2010) sets _WIN32_WINNT to the constant for Windows 7 if nothing is
set. This could lead to the libav configure script detecting and
using functions only present in Windows 7 or newer, which in most
cases isn't desired. If the call
