Em Saturday 02 March 2013, Àlex Fiestas escreveu:
> Just a reminder that we should buy the plane tickets ASAP so we can get the
> cheaper deals. The sprint is only 40 days away.
>
> See you in Brno !
I already bought mine a couple of weeks ago :-) See you in Brno.
--
Lamarque V. Souza
K
Just a reminder that we should buy the plane tickets ASAP so we can get the
cheaper deals. The sprint is only 40 days away.
See you in Brno !
So, in the end, we have two solutions for projects that are pro C++11:
1) Use the qglobal.h macros as suggested by Thiago.
If one desires to know of the features in cmake, it would be enough to parse
the output of:
gcc -std=c++11 -fPIE -E -dM -I$QTDIR/include -include QtCore/qglobal.h \
-xc++
On Saturday 02 March 2013 00:37:25 Ivan Čukić wrote:
> > gcc -std=c++11 -fPIE -E -dM -I$QTDIR/include -include QtCore/qglobal.h
> > -xc++ /dev/null | grep Q_COMPILER
> >
> > That will give you the full listing of detected features, matching exactly
> > what will be available at compile-time.
>
>
On Sat, Mar 2, 2013 at 9:15 AM, Rolf Eike Beer wrote:
> Am Freitag, 1. März 2013, 16:06:38 schrieb Ivan Čukić:
> > Hi all!
> >
> > The CMake modules for detecting C++11 features are going to get in
> kdereview
> > soon. The target for the repository is kdesupport.
>
> There is a feature request fo
Am Freitag, 1. März 2013, 16:06:38 schrieb Ivan Čukić:
> Hi all!
>
> The CMake modules for detecting C++11 features are going to get in kdereview
> soon. The target for the repository is kdesupport.
There is a feature request for CMake itself to provide such a module, and I
have half of the implem
