Re: [CMake] ExternalProject_add and add_subdirectory in one step

Hi Franz. The "canonical" approach to ExternalProject is to use a "superbuild" setup. Design your top-level CMakeList so that it *only* contains ExternalProject_add() calls, treating your "original" project as just another external project. Build the superbuild once, getting all the dependencies d

[CMake] "Modern" CMake with Qt5 and packaging on OS X

We are migrating our application from Qt4 to Qt5. In the past we had a combination of a cmake script and shell script that would fix-up the application bundle on OS X. This does not seem to work any more in that we are missing the platform plugins and a few other items. Are there any examples of

[CMake] CMP0026 - Disallow use of the LOCATION target property

Hi, I have a question of policy CMP0026. Our project currently is on CMake 2 and we are planning to move to CMake 3. When we run CMake3.1.1, we get get a few warnings due to the policy CMP0026, "Disallow use of the LOCATION target property". Even though with those warnings, our cmake scripts stil

Re: [CMake] Mixed linking

Hello again. Thanks for the answers. To Stephen Kelly: >> Here are a few questions for the list (hoping someone more knowledgable >> than me will read this and help): >> >> 1) Am I right when I say CMake, Qt and static linking don?t mix ? >They should mix fine. Alright, I won't give up just ye

Re: [CMake] Mixed linking

> > But I just don't know how to include the plugins. Actually, I always get > the error about the platform plugin (cocoa in my case). Any tips ? For Windows it’s like this: #if defined(Q_OS_WIN) && defined(QT_STATIC) #include Q_IMPORT_PLUGIN(QWindowsIntegrationPlugin) #endif Best, Norbert.

Re: [CMake] "Modern" CMake with Qt5 and packaging on OS X

On 06/02/2015 14:00, Michael Jackson wrote: Hi Mike, We are migrating our application from Qt4 to Qt5. In the past we had a combination of a cmake script and shell script that would fix-up the application bundle on OS X. This does not seem to work any more in that we are missing the platform

Re: [CMake] CMP0026 - Disallow use of the LOCATION target property

Jifeng ZHANG wrote: > Hi, > > I have a question of policy CMP0026. Our project currently is on CMake > 2 and we are planning to move to CMake 3. Lot's of questions on that lately. Someone opened the floodgates it seems :). > When we run CMake3.1.1, we get get a few warnings due to the policy >

Re: [CMake] Mixed linking

Norbert Pfeiler wrote: >> >> But I just don't know how to include the plugins. Actually, I always get >> the error about the platform plugin (cocoa in my case). Any tips ? > > > For Windows it’s like this: > > #if defined(Q_OS_WIN) && defined(QT_STATIC) > #include > Q_IMPORT_PLUGIN(QWindowsI

[CMake] Mixed linking

Hi, Apologies that this won't tread correctly (and for directly CC'ing the three participants); I only signed up to the mailing list after I saw this conversation. I'm an MSYS2 developer (and I occasionally hack on Qt build system issues). I've spent a lot of time working on our qt5 and qt5-static

Re: [CMake] Mixed linking

> > Norbert Pfeiler wrote: > > Currently you have to define »QT_STATIC« > You shouldn't need to do this. If you use MSYS2's > mingw-w64-{i686,x86_64}-qt5-static then that will be defined for you. I have both *-qt5 (for dev) and *-qt5-static (for deploy) installed and append the root of qt5-static