[Qt-interest] Proposal: qmake shouldn't specify warning options when neither warn_on nor warn_off have been specified

[Andreas Pakulat]

On 04.04.10 03:42:09, Nikos Chantziaras wrote:
> Currently, qmake only understands warn_on and warn_off in CONFIG.  For 
> warn_off, it uses a compiler option that completely disables all warning 
> options.  warn_on on the other hand uses an option that enables all 
> warnings.  There's no middle-ground, namely not using any 
> warning-related compiler options and let the compiler only issue 
> warnings that it deems serious enough to emit at its default warning level.
> 
> My proposal here is that if the project file doesn't specify warn_on or 
> warn_off, then qmake should generate Makefiles that do not contain any 
> warning-switches for the compiler.

Sending a mail to this list doesn't really get you anywhere. Either file
a feature request on bugreports.qt.nokia.com or clone the Qt git
repository, implement a patch and send a merge request.

Andreas

-- 
You will have good luck and overcome many hardships.