Re: [CMake] Copying DLLs to output directory

Hi, you can use generator expression in a post build rule to copy the dll file to the same target dir as the target you link it with. The easiest way to do this is to properly define all 3rd party libraries as imported targets that contains both, the lib and the dll file. Sadly, the FindQt4 on

[CMake] Is anyone working on a FASTBuild Generator?

And if not, is there any information on how an outside developer might begin work on a custom generator? I'm just a student, so I'm not sure how much time I have to dedicate to something like this, but I am interested in seeing what's involved. Link to FASTBuild: http://www.fastbuild.org/docs/home

Re: [CMake] Copying DLLs to output directory

Well basically, if you are on windows cmake can find the .lib file but then I wrote some code for each 3rd party library that attempts to find the .dll files. Once those files are found I create the copy files targets for each DLL. Mike Jackson On Oct 27, 2014, at 11:17 PM, J Decker wrote: >

Re: [CMake] Copying DLLs to output directory

how does that work with say openwatcom? On Mon, Oct 27, 2014 at 7:51 PM, Michael Jackson < mike.jack...@bluequartz.net> wrote: > I use a copy rule for the DLLs during the build which finds the DLL and > then copies it to the Debug or Release directory. You are welcome to the > macro that we use f

Re: [CMake] Copying DLLs to output directory

I use a copy rule for the DLLs during the build which finds the DLL and then copies it to the Debug or Release directory. You are welcome to the macro that we use for our project. If there is an easier way with Cmake 3.0.x I would love to hear about it. Thanks Mike Jackson On Oct 27, 2014, at

Re: [CMake] Copying DLLs to output directory

If you add install rules, you can get a runnable package... and kill having to configure things to package in one step. Install can just target 'output' or some relative directory to the build directory, it doesn't have to be the final install target. On Mon, Oct 27, 2014 at 6:55 PM, Robert Daile

Re: [CMake] Refer to all debug or release targets with generator expressions

That's a cute solution. Never thought of it. Generator expressions are really advanced & handy now. I like it. On Mon, Oct 27, 2014 at 7:14 PM, Daniel Schepler wrote: > I think this should work: > > $<$>:${my_release_libs}> > -- > Daniel > > -Original Message- > From: CMake [mailto:cmake-

[CMake] Copying DLLs to output directory

This actually used to be a very difficult problem to solve. However, to debug in visual studio it's essential. If I have DLLs located in third party directories OR from targets that I depend on, those must all be copied to the directory of the executable I'm debugging in order for those DLLs to be

[CMake] Adding a new language for a multiple language project - CMAKE_AR problem(?)

Hello, I'm trying to create a simple exercise, a definition for a virtual language "X" that will be used side-by-side with C and C++. There are some restrictions on the level of compatibility with C/C++. For instance, the objects of this language aren't directly compatible with C and C++ but then

Re: [CMake] Refer to all debug or release targets with generator expressions

I think this should work: $<$>:${my_release_libs}> -- Daniel -Original Message- From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Dailey Sent: Monday, October 27, 2014 5:12 PM To: CMake Subject: Re: [CMake] Refer to all debug or release targets with generator expressions

Re: [CMake] Refer to all debug or release targets with generator expressions

I forgot to give a more concrete example. Consider this: add_library( Foo INTERFACE ) target_link_libraries( Foo INTERFACE $<$:${lib_debug}> $<$:${lib_release}> $<$:${lib_release}> $<$:${lib_release}> ) Must I do it like this for each and every configur

[CMake] Refer to all debug or release targets with generator expressions

I know that when defining link libraries, I can do this: $<$:${my_debug_libs}> The debug libraries will be the same for all debug targets. Likewise with Release targets. Is there a way to refer to *all* release targets using generator expressions? There are 3 release configurations that ship with

[CMake] FOSDEM 2015 Desktops DevRoom Call for Talks

Hello, --8<--- FOSDEM is one of the largest gatherings of Free Software contributors in the world and happens each February in Brussels (Belgium). One of the tracks will be the Desktops DevRoom (formerly known as “CrossDesktop DevRoom”), which will host Desktop-related ta

[CMake] CMP0020 warning

The warning message for CMP0020 seems to be completely random as to where you actually have to set the policy. Im not getting the warning on my main executables, but cant seem to get rid of it on any of my Qt based unittests (using gmock/gtest ) I have the following line, in various places in t

[CMake] CMake, armcc and Ninja workarounds and problems

A summary of limitations with (mostly) armcc and Cmake, primarly using Ninja generator. (Note that this is referring to two emails and add a new problem.) The workarounds where applicable are listed, as well as possible corrections/enhancements in CMake. I will probably open issues later, maybe

Re: [CMake] OS X Fortran flags

On 27/10/2014 13:17, Brad King wrote: Hi Brad, On 10/24/2014 04:29 PM, Bill Somerville wrote: Sorry, I am struggling with this. I have copied the Darwin-GNU-Fortran.cmake file into my project modules directory and patched it as you suggested. Sorry, I meant the Modules directory of your CMake i

Re: [CMake] OS X Fortran flags

On 10/24/2014 04:29 PM, Bill Somerville wrote: > Sorry, I am struggling with this. I have copied the > Darwin-GNU-Fortran.cmake file into my project modules directory and > patched it as you suggested. Sorry, I meant the Modules directory of your CMake installation. > The good news is that it w