QT5.7 configure.exe needs to show -no-warnings-are-errors option
-
When I tried to build a static version of QT5.7 from qt-everywhere-oppensource-src-5.7.0.zip using the gcc g++ C++11 compiler, and windows 7, configure.exe would terminate early because gcc would generate a zero as null pointer constant warning from one of the qmake header files, which would then cause g++ to exit because configure.exe compiled it with the -Werror option, which generates an error on any warning.
Looking through the configure.exe file, I found that it accepts a -no-warnings-are-errors option. This option is not listed in any documentation or listed using the -h option.
Once I added this option, configure.exe successfully built qmake and the other make files.I recommend Qt fix this bug in configure.exe -h. It would have saved me a lot of grief.
-
When I tried to build a static version of QT5.7 from qt-everywhere-oppensource-src-5.7.0.zip using the gcc g++ C++11 compiler, and windows 7, configure.exe would terminate early because gcc would generate a zero as null pointer constant warning from one of the qmake header files, which would then cause g++ to exit because configure.exe compiled it with the -Werror option, which generates an error on any warning.
Looking through the configure.exe file, I found that it accepts a -no-warnings-are-errors option. This option is not listed in any documentation or listed using the -h option.
Once I added this option, configure.exe successfully built qmake and the other make files.I recommend Qt fix this bug in configure.exe -h. It would have saved me a lot of grief.
@BK_Broiler Asking in this forum for such a change will most probably not work. You should create a bug-report.
-
Hi,
What header gave you that error ?
-
When I tried to build a static version of QT5.7 from qt-everywhere-oppensource-src-5.7.0.zip using the gcc g++ C++11 compiler, and windows 7, configure.exe would terminate early because gcc would generate a zero as null pointer constant warning from one of the qmake header files, which would then cause g++ to exit because configure.exe compiled it with the -Werror option, which generates an error on any warning.
Looking through the configure.exe file, I found that it accepts a -no-warnings-are-errors option. This option is not listed in any documentation or listed using the -h option.
Once I added this option, configure.exe successfully built qmake and the other make files.I recommend Qt fix this bug in configure.exe -h. It would have saved me a lot of grief.
@BK_Broiler said in QT5.7 configure.exe needs to show -no-warnings-are-errors option:
Once I added this option, configure.exe successfully built qmake and the other make files.
To clarify: Do you mean you ran configure.exe directly? Or did you run configure.bat from the source root, which then ran configure.exe?
Also, can you please share the full list of configuration options that you used?
-
My mistake, configure.exe -h does list the -no-warnings-are-errors option, it's just buried between 3 other listings in the middle of the print out
