Using nullptr instead of Q_NULLPTR
luigi.toscano at tiscali.it
Thu Aug 13 14:07:21 BST 2015
On Thursday 13 of August 2015 15:01:16 Ivan Čukić wrote:
> > What I don't like in this story is that we set up a rule, an promise with
> > users, which was broken and now it's like it does not matter.
> Yes, we did set up the rule requirements for gcc 4.5 and MSVC10 back in
> Since then, we broke the rule and increased to MSVC11 (VS2012).
> Now, we can increase, if we want to, the gcc requirement to 4.6.
> If you think that the additional work of writing a patch, then
> increasing the compiler version requirement, and then reverting the
> patch is warranted, it is fine by me.
> As Lamarque pointed out, gcc 4.6 is required for Qt 5.1. KF5 requires
> Qt 5.3. If someone is able to compile Qt, he will be able to compile
> KF5 - I guess that is the reason this issue has passed unnoticed for
> this long.
I apologize, I mixed up two different emails that came today on a similar
topic. There is nothing to discuss on this, given the requirement of Qt 5.1.
Please take a look also at "Minimum supported version of MSVC for frameworks"
More information about the kde-core-devel