On 14/05/2020 10:48, Steffen wrote:
On Wednesday 13/05/2020 at 10:41, Mladen Turk wrote:
Hi,
Please tell me what is the exact issue with dsw/dsp/mak.
Hard to work with and maintain, but if someone
founds it usabe, then fine.
When I look at the cmake in current HTTP/Apr GA, it is not good maintained
and after 6 years years not all is build and has limitations.
I said I'd like to bring that cmake stuff up to notch and make it
fully workable, using VS existing tools (nowadays coming directly
as part of VS (even Community edition), like CMake, Python, Ninja ...)
There is even entire new build ecosystem ...
https://github.com/microsoft/vcpkg/tree/master/ports/apr
https://github.com/microsoft/vcpkg/tree/master/ports/apr-util
So keep both, it hurts nobody ! And there a guys who maintain it (easy).
OK. My intention was just to cleanup the things, but since
so many folks are still having VStidio 6.0 around ... fine :D
3. Drop all that APR_HAS_ANSI_FS and APR_HAS_UNICODE_FS
Code in trunk need at least _WIN32_WINNT=0x0601 API
-1 be aware that still 600 boxes are used, special in companies.
Backward API compatibility does not mean backward platform compatibility.
Limiting windows to stick to an old WINAPI is restricting progress.
There are bunch of new WINAPI, we still have to emulate to support
those archaic platforms.
Like Ivan said, already been discussed.
Regards
Regards
--
^TM
