no match for 'operator>' error with Qt 5.11.2 and mingw32-5.3.0

[mrjj]

Hi
Could you try delete build folder and add
CONFIG += c++1z
to the .pro file and see if that helps ?

[VRonin]

Probably better to ask the question directly here: https://github.com/parihaaraka/sqt/issues

[fortress]

@mrjj
Hello
I'm trying this, remained the same mistakes.

[fortress]

@VRonin
if nothing helps, I'll write there.
Since the error is related to the source files of the environment, and not the project, I believe that the problem is either in my environment or in the project settings.

[aha_1980]

@fortress you have MinGW 5.3.0, which is already a bit older. May it be you need a newer compiler?

[fortress]

@aha_1980 my Maintenance tool for qt show that there is Qt 5.11.2 pre-built components for mingw32-5.3.0 (32-bit) (installed). Therefore i install tools/mingw32-5.3.0 toolchain. It is possible to install mingw 7.3.0 (64-bit), but my system is 32-bit and no pre-built comoponents for this toolchain.

[aha_1980]

Hi @fortress,

If I remember correctly, there will be no pre-build 32 bit MinGW version starting from Qt 5.12.

You can still compile Qt from source yourself, of course.

Regards

[fortress]

Hi @aha_1980, now i have install Qt 5.11.2 for both mingw32-5.3.0 and msvc 2015:
and toolchain mingw 5.3.0
Also installed MSVC 2015 Community edition.
Building project in QtCreator with toolchain MSVC 2015 is successfull. Also some libs (as suggested by the author) on which this project depends, are built with msvc compiler. So, its only way to build this project is use MSVC toolcain.

But, i suppose if i have Qt pre-built for mingw and mingw same version, all must compile without errors. So, i suppose a problem may be either building environment or project settings (compiler/linker flags, etc).

I think I can try to create a simple project that will use <thread> and check how it will be compiled.

[aha_1980]

Hi @fortress,

your conclusion is good, however neiter MSVC 2015 nor GCC 5.3 are full C++17 capable. So some C++17 features might work, others will not.

I think I can try to create a simple project that will use <thread> and check how it will be compiled.

Probably a good idea :)

[aha_1980]

Hi @fortress,

your conclusion is good, however neiter MSVC 2015 nor GCC 5.3 are full C++17 capable. So some C++17 features might work, others will not.

I think I can try to create a simple project that will use <thread> and check how it will be compiled.

Probably a good idea :)