[Development] Proposal for Qt 5.10 platforms and configurations changes

Mat Sutcliffe oktal3700 at gmail.com
Sun Apr 30 00:14:54 CEST 2017


On 29 April 2017 at 21:31, Thiago Macieira <thiago.macieira at intel.com>
wrote:

> On Friday, 28 April 2017 12:50:41 -03 Mat Sutcliffe wrote:
> > tldr: MSVC expects to see linker symbols for inline member functions of
> > exported classes. When such a function is defined within #ifdef
> > Q_COMPILER_foo (being a macro that is defined for 2017 but not 2015) this
> > could mean linker errors. Unknown if this effect has actually been
> observed
> > or is merely theoretical.
>
> Thanks Mat.
>
> If this is the only issue, then it's only a potential issue that will not
> affect us. There's exactly one Q_COMPILER_foo macro that is in 2017 that
> isn't
> in 2015:
>         Q_COMPILER_CONSTEXPR
>
> And the totality of its use in public headers, aside from the definition in
> qcompilerdetection.h, is...


It also controls whether Q_DECL_CONSTEXPR expands to constexpr or nothing.
But I don't think that should alter whether or not a function is inline,
because functions declared with Q_DECL_CONSTEXPR should already be inline
anyway.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170429/77a94781/attachment.html>


More information about the Development mailing list