Hi Elvis,

If you've got kdemacors.h in /usr/include (for instance because you've also got a kde4 dev env) then you won't encounter the error. The issue is that the expanded list of includes is enclosed in "", which breaks the build.

On Mon, 25 May 2015, Elvis Stansvik wrote:

2015-05-25 16:13 GMT+02:00 Boudewijn Rempt <b...@valdyas.org>:
      Weird, it worked for me:

      https://paste.kde.org/pmvwwhyqp -- in fact, the header file isn't used or 
needed in the example at all.


I seem to be getting the same result as Alex (I think): 
https://paste.kde.org/pke2ztbok

I'm a little pussled by your paste, what is wrong with the compile line? You do 
have -I/usr/include/KF5/KDELibs4Support in there, which should
contain kdemacros.h?

Elvis
 


      On Mon, 25 May 2015, Alex Merry wrote:

            On Monday 25 May 2015 15:31:52 Boudewijn Rempt wrote:
                  http://www.valdyas.org/~boud/vc-cmake-3.tgz is as minimal as 
I know how to
                  make it: you still need qt, KDELibs4Support and 
extra-cmake-modules
                  installed. After that, running cmake and make VERBOSE=1 will 
give the
                  exact problem I've got.


            I get compiler issues with that, but the problems I'm getting are 
because
            KoOptimizedCompositeOpFactoryPerArch.cpp doesn't include
            KoOptimizedCompositeOpFactoryPerArch.h, which doesn't have a ; 
after the class
            definition, and when I fix those I get multiple definition errors 
for
            Bla::bla(). The includes are ending up on the command line just 
fine.

            This is true no matter if I use cmake-3.0.2, cmake-3.1.3 or 
cmake-3.2.2.

            Alex

      _______________________________________________
      calligra-devel mailing list
      calligra-de...@kde.org
      https://mail.kde.org/mailman/listinfo/calligra-devel



_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Reply via email to