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
> The solution is to have missing services then?
IMO, better not have something than to lie about it. It is like that mainly
for the systems for which don't really want kde workspaces, but rather just
applications (having activities, kwin, etc. under windows or mac is not a
desire of ours).
A
On sexta-feira, 1 de março de 2013 23.11.53, Ivan Čukić wrote:
> > Why do you need that? Are you adding source files conditionally, depending
> > on whether the compiler supports certain features?
>
> Yes, as I said, the library builds with any C++ compiler, but the service
> requires at least gcc
> Why do you need that? Are you adding source files conditionally, depending
> on whether the compiler supports certain features?
Yes, as I said, the library builds with any C++ compiler, but the service
requires at least gcc 4.5 equivalent feature set.
The service can not use #error since that
On sexta-feira, 1 de março de 2013 19.25.40, Ivan Čukić wrote:
> One needed feature forgotten, so I'm starting with it:
>
> Is it possible for cmake scripts to test the Qt defines?
Why do you need that? Are you adding source files conditionally, depending on
whether the compiler supports certain f
One needed feature forgotten, so I'm starting with it:
Is it possible for cmake scripts to test the Qt defines?
Namely, the kactivities repository is consisted of a few parts that have (as
previously agreed) different c++ feature requirements
- the library - compilable with any Qt/KDElibs supp
On sexta-feira, 1 de março de 2013 17.29.26, Martin Gräßlin wrote:
> > Why can't you use the #defines from QtCore?
>
> because we don't use Qt 5 yet?
You can simply copy the necessary sections of qcompilerdetection.h into your
code if you're still using Qt 4. By construction, your code isn't using
On sexta-feira, 1 de março de 2013 18.28.33, Ivan Čukić wrote:
> > Can we discuss whether such module should be used?
>
> Naturally.
>
> > > Why can't you use the #defines from QtCore?
>
> From my POV:
> - it is not documented - at least, I couldn't find it in Qt 4.8 docs, nor
> 5.0 (might be a fa
> Can we discuss whether such module should be used?
Naturally.
> > Why can't you use the #defines from QtCore?
>From my POV:
- it is not documented - at least, I couldn't find it in Qt 4.8 docs, nor 5.0
(might be a fault of qt-project.org's search mechanism)
- it is not extensible - it cover
On Friday 01 March 2013 08:12:59 Thiago Macieira wrote:
> On sexta-feira, 1 de março de 2013 16.06.38, Ivan Čukić wrote:
> > p.s. Please don't start a discussion on whether C++11 should be used or
> > not, we have had that already, and everything we are doing is in
> > accordance with the decision
On sexta-feira, 1 de março de 2013 16.06.38, Ivan Čukić wrote:
> p.s. Please don't start a discussion on whether C++11 should be used or
> not, we have had that already, and everything we are doing is in
> accordance with the decisions made then.
Can we discuss whether such module should be used?
Adding Rolf, as he was working on this:
http://quickgit.kde.org/?p=scratch%2Fdakon%2Fcmake-cxx11.git
On Fri, Mar 1, 2013 at 3:06 PM, Ivan Čukić wrote:
> Hi all!
>
> The CMake modules for detecting C++11 features are going to get in
> kdereview
> soon. The target for the repository is kdesupport.
Hi all!
The CMake modules for detecting C++11 features are going to get in kdereview
soon. The target for the repository is kdesupport.
To clone it, just do the regular: git co kde:cxx11-cmake-modules
It would be awesome if our regular CMake experts could give me a few hints on
what should be
16 matches
Mail list logo
