[CMake] Is this the proper way to define a package config?

I have a local package of boost built on Windows. It is always relative to the root of my project at a consistent structure and location. I wanted to define an import target for this and thought it might be best to define a BoostConfig.cmake package config file at the root of the boost lib director

[CMake] Interface include directories

I'm ramping up on CMake 3.0 and I like that you've added INTERFACE_INCLUDE_DIRECTORIES. Is this automatic when I add a dependency on another target? For example, suppose I have two targets A and B. And in my target link libraries for B, I specify A. B now depends on A. Will I also inherit its inter

Re: [CMake] Specifying different compilers for subsets of a project

Hi Chuck, Thanks for your e-mail. Yes, the different build directory strategy is definitely the clean way to do this. However, it is my experience that folks not familiar with CMake tend to get a knee-jerk reaction when required to configure and build seperately. Especially, when something like

[CMake] cache variables from compiler checks

I noticed something odd... If I delete the cache variable CMAKE_STRIP, then re-run cmake, it doesn't come back. If I delete the build/CMakeFiles directory, re-run cmake, it'll come back. Is that intentional? I have a dashboard build where I was re-configuring with a different initial CMakeCac

Re: [CMake] Specifying different compilers for subsets of a project

Hi George, > The obvious way to compile front-end tools is to create another directory, > e.g., "front-end-build" and run cmake therein to re-configure and build > with a front-end compiler. > > However, since only a relatively small subset of the files needs to be > compiled for the front-end,

Re: [CMake] Tests not added to CTestTestfile.cmake on OS X

Hello again, I have fixed this issue. Using Debug and Release as configuration did create the tests correctly, I just didn't notice it. So the problem was Debug-/Release-iphonesimulator as configuration. When CTest is run by XCode and using the iPhone Simulator SDK, "-iphonesimulator" is attach

Re: [CMake] [CPack] RPM generator and directory symlink

Thanks a bunch! I was gonna miss a deadline because of that issue and you really saved the day! On 16 Oct 2014, at 09:06, Domen Vrankar [via CMake] wrote: > > > A workaround that you could use is to specify something like > > > > set(CPACK_RPM_bin_USER_FILELIST "%config /subdir") > > > > and

Re: [CMake] [CPack] RPM generator and directory symlink

Just to confirm that your suggestion does indeed work. I did it without specifying a component since the RPM generator does not have that feature switched on by default iirc: Thanks! - -- Luc J. Bourhis -- View this message in context: http://cmake.3232098.n2.nabble.com/CPack-RPM-gener

Re: [CMake] INSTALL DIRECTORY patterns highly confusing

Of course. The problem comes when somebody is used to languages that encourage single-quoted strings (e.g. python or shell) or which have tight syntax and abort on mistakes like this. This lack of early feedback coupled with the terse doc and strange semantics means that when something doesn't wo

[CMake] Tests not added to CTestTestfile.cmake on OS X

Dear all, I'm encountering a problem when adding tests with add_test for CTest on OS X 10.9.4. The CTestTestfile.cmake, which should contain the tests, only has the header, but is empty otherwise (the ones in the directories above, just include the other directories correctly). On Windows wit

[CMake] Philosophy with Tests for Beginners

Hi! I have a question regarding handling with tests. currently my sources are build together with tests. the tests in the binary location could be executed via make test or ctest. So far so good. Considering our Jenkins / Build Configurations i want to seperate build and tests. That means i wan

Re: [CMake] INSTALL DIRECTORY patterns highly confusing

Hi Dan. Single quotes have no special meaning in CMake syntax, so it was literally treating them as part of the pattern. This is not special to the install() command in any way, it's just how CMake works. Petr On Thu, Oct 16, 2014 at 4:13 AM, Dan Kegel wrote: > > This turned out to work for me

Re: [CMake] [CPack] RPM generator and directory symlink

> > A workaround that you could use is to specify something like > > > > set(CPACK_RPM_bin_USER_FILELIST "%config /subdir") > > > > and this will force CPackRPM to treat the symlink as a config file. > > What is the meaning of bin in the middle of that variable name? CPACK_RPM_USER_FILELIST is us