On Fri, Dec 10, 2021 at 8:47 AM Ivan Zhakov <i...@visualsvn.com> wrote:
>
> On Thu, 2 Dec 2021 at 22:33, Mladen Turk <mt...@apache.org> wrote:
>>
>> Issues with API beyond Windows SDK 7.1.A
>> (Latest one supporting Windows 7.1sp1)
>>
>> It just means apr-2 won't be able to run on anything below Windows 10.
>> There a lots of code you added recently that uses that new API
>> breaking also possibility to port that back to 1.7.x, 1.6.x branch.
>>
>> Dunno, maybe that's a good thing after all.
>>
> We discussed some time ago that minimum version for APR trunk is  Windows 
> 7/Windows Server 2008 R2:
> https://lists.apache.org/thread.html/de5af5247324db3e0636a654f2c23d3ff3a94a91f9d35adf5402b927@%3Cdev.apr.apache.org%3E
>
> As far I'm aware APR trunk should work fine in Windows 7/Windows Server 2008 
> R2.

Correct, although we should begin ignoring these EOL operating systems
which expired
2 years ago at this point.

Oct 10, 2023 is the end of Extended EOL of Windows Server 2012 and Windows 8.1,
and  by the end of next year, they should also be dropped.

As we call API functions that aren't present before the Windows 10
API, we simply need
to add new dll's such as ws2tcpip.dll to misc/win32/misc.c and api
function prototypes
to include/arch/win32/apr_arch_misc.h.

Right now we should be axing a number of these in apr_arch_misc.h
which have been
present since Server 2012 for the apr 2.0 master branch.

There's a lot of confusion; we should simply define WIN32_WINNT now as
0x0A0A and
be done with it. We simply need to do the work around missing calls.
And will need a
somewhat more dynamic expression for things like APR_HAS_ macros which depend
on the -current- os level.

Reply via email to