[CMake] Problems with CMP0037

Hi, I'm a project maintainer. I just upgraded to CMake 3.0.2 and now I'm getting this: CMake Warning (dev) at CMakeLists.txt:284 (add_executable): Policy CMP0037 is not set: Target names should not be reserved and should match a validity pattern. Run "cmake --help-policy CMP0037" for p

Re: [CMake] Copying DLLs to output directory

I've solved the problem that way in the past. What you do is copy the .user file and make the environment setup driven by configure_file() in CMake. That way at CMake configure time you can create a .user file for each .VCPROJ that has PATH setup to point to third party BIN directories as needed.

[CMake] Variable for AUTOMOC files?

I am setting and using CMAKE_AUTOMOC to on, however, for Qt4+Cmake 2.8 builds, I would put the moc files into a separate folder (Visual Studio) using source_group("Generated Files" FILES ${qtproject_MOC_SRCS}) Where qtproject_MOC_SRCS was defined via QT4_WRAP_CPP(qtproject_MOC_SRCS ${mocheaders}

Re: [CMake] What generator(s) should be used for MinGW-w64?

On 2014-10-30 14:07-0700 Alan W. Irwin wrote: [...] Furthermore, there is an MSYS2 project (a completely independent project from MSYS, see ) which _is_ API-compatible with MinGW-w64 since it is built with that compiler. The combination of MinGW-w64 an

[CMake] Extracting the configure and generate command

Once I have configured and generated a CMake project, is there a way to extract that into a command? So, let's say I have configured and generated a project using the CMake GUI. I am then able to extract (somehow) the full configure/generate command which looks like this: cmake -DOPTION_1=ON -DOPT

Re: [CMake] Copying DLLs to output directory

On 01/11/2014 14:15, Cory Quammen wrote: Mike, You can modify or override the PATH variable in Visual Studio by pulling up the properties for the startup project and going to Configuration Properties -> Debugging, and add an entry for your preferred PATH under the "Environment" setting. By d

Re: [CMake] Copying DLLs to output directory

Mike, You can modify or override the PATH variable in Visual Studio by pulling up the properties for the startup project and going to Configuration Properties -> Debugging, and add an entry for your preferred PATH under the "Environment" setting. By default, this will merge your PATH with the PAT

Re: [CMake] Copying DLLs to output directory

On 01/11/2014 14:02, Michael Jackson wrote: Hi Michael, I agree that if the FindQt4 would enumerate the DLLs that would be great and simply get ride a bunch of this home-brew code that I have to write for each library. Getting the Plugins would also be a great help also since I have to grab a

Re: [CMake] Copying DLLs to output directory

I agree that if the FindQt4 would enumerate the DLLs that would be great and simply get ride a bunch of this home-brew code that I have to write for each library. Getting the Plugins would also be a great help also since I have to grab a few of those. the FindQt5 module does this I think. Chee

Re: [CMake] Copying DLLs to output directory

The thing I could never figure out is how to set the PATH for the Visual Studio Project/Solution. That is what I need. If I only had a single version of Qt on my system it would be very straight forward. Just set the PATH environment variable using the standard windows mechanism for doing that a

Re: [CMake] Copying DLLs to output directory

Am 31. Oktober 2014 20:51:55 MEZ, schrieb Bill Somerville : >On 31/10/2014 19:42, Michael Jackson wrote: >> Never said it was pretty, but here is the code I use for Qt4 based >projects. I think I had to revamp a lot of this for Qt5. I call it like >so: >> >> CMP_COPY_QT4_RUNTIME_LIBRARIES( "QtCo