Page 2 of 2

Building FAR Manager

Posted: Fri 03 Feb, 2017 22:48
by 2useven10

Latest post of the previous page:

ChemicalDruid wrote: Hmmm... _WIN32_WINNT seems to be 0x0502 on my Windows 10.0.14393
It is not about the system it is about SDK version.
0x0502 version used in sdkddkver.h if neither WINVER nor _WIN32_WINNT was defined.
It looks like __GNUC__ is not defined in gcc you used, otherwise it should be defined in headers.hpp

Code: Select all

# undef WINVER
# undef _WIN32_WINNT
# undef _WIN32_IE
# define WINVER       0x0603
# define _WIN32_WINNT 0x0603

Building FAR Manager

Posted: Sat 04 Feb, 2017 13:41
by ChemicalDruid
DrKnS wrote: We cannot test and support every mingw distribution in the universe - take the one from the 2useven10's link above, it "just works".
I am using the latest MSYS2 64bit installation with the mingw-w64-x86_64-toolchain and base-devel packages on Windows 10 - is that not a distribution worthy of support?

Building FAR Manager

Posted: Sat 04 Feb, 2017 13:45
by ChemicalDruid
2useven10 wrote: It is not about the system it is about SDK version.
0x0502 version used in sdkddkver.h if neither WINVER nor _WIN32_WINNT was defined.
It looks like __GNUC__ is not defined in gcc you used, otherwise it should be defined in headers.hpp
When using a barebones C++ source file, __GNUC__ is output as 6 below:

Code: Select all

    printf("__GNUC__ = %ld\n",__GNUC__);

Building FAR Manager

Posted: Sat 04 Feb, 2017 14:26
by DrKnS
ChemicalDruid wrote: is that not a distribution worthy of support?
I have no idea.
You have mentioned windows 10 several times, does that mean it's a 'standard' toolset there?

Building FAR Manager

Posted: Sat 04 Feb, 2017 20:09
by ChemicalDruid
DrKnS wrote:
ChemicalDruid wrote: is that not a distribution worthy of support?
I have no idea.
You have mentioned windows 10 several times, does that mean it's a 'standard' toolset there?
As the Windows Subsystem for Linux is now released, albeit marked as beta, the MinGW environment, especially inside the MSYS2 shell, is pretty standard for non-VS uses, IMHO.

Anyway, the workarounds I mentioned have fixed the issues, so what I was looking for was mostly an opinion or two about what could cause the issues in an otherwise vanilla system with pretty standard setup software and settings.