[Development] QT_DEPRECATED_SINCE and QT_DISABLE_DEPRECATED_BEFORE
Rohan McGovern
rohan.mcgovern at nokia.com
Thu Nov 3 00:08:47 CET 2011
Thiago Macieira said:
> On Wednesday, 2 de November de 2011 10:53:40 bradley.hughes at nokia.com wrote:
> > On 02 Nov, 2011, at 01:29 , ext Rohan McGovern wrote:
> > > I also noticed that Brad recently added the ability to pass through
> > > options like -Werror into configure [
> > > http://codereview.qt-project.org/7487 ]. I intend for us to attempt using
> > > that in CI as soon as we have newer gcc available (>= 4.6), which will be
> > > soon. Any opinions on exactly
> > > the appropriate -W* options would be appreciated :)
> >
> > I would love to see us fix all the -Woverloaded-virtual warnings… there are
> > tons of them :(
>
> I'd like to enable -Werror by default if you use -developer-build. That way,
> everyone of us is on the same boat, modulo compiler version.
>
> The CI system doesn't (or didn't use to) build in developer mode, but if Rohan
> says it's a goal, I'm not going to say no :-)
Nowadays it builds roughly 50% in developer mode and 50% not, as there
was no other solution forthcoming to exercise all those autotests which
need private symbols. Some Qt modules have very little test
coverage in the non-developer configuration, unfortunately.
More information about the Development
mailing list