[CMake] Create space delimited string with $ genex

Hello, in my build process I need to call a compiler like tool with the same include directories as a certain target. I tried the following: cmake_minimum_required(VERSION 3.2) project(cmake-genex C) add_library(dummy dummy.c foo.c) target_include_directories(dummy PUBLIC foo bar) set(prop "$"

Re: [CMake] Icon and Launch image support for iOS apps

On 03-Jul-15 13:00, Daniel Dewald wrote: Howdy folks, I’m currently in the process of converting our internal projects from premake to cmake. The process is almost complete. However I’ve been stuck on a seemingly simple problem the last few days that I could need some help /advise on. Since

[CMake] Sphinx warning.

The latest version of Sphinx generates this warning when building CMake from the master: "WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default." See: https://git

Re: [CMake] cmake-qt: controlling includes order

Bill Somerville wrote: > Also this is all due to a > Mac issue where having MacPorts Qt4 installed causes it to be pulled in > when some other MacPorts library is used, in this case FFTW3. Most of > our developers work on Windows and Linux and are not going to know that > this abomination is requi

Re: [CMake] linking static libs into shared libs on Linux

On 07/08, Dan Kegel wrote: > So maybe the yasm source needs to have a keyword or two > added to select PIC addressing mode? > > Random googling finds suggestions at > http://cvs.tortall.net/pipermail/bug-yasm/2011-October/86.html Thanks for all the help. Upon further debugging with 'make VERB

Re: [CMake] Finding internal libraries

John LaGrone wrote: > However, if I try to build the > examples and the library at the same time, the configuration fails > because it cannot find the library "foo" for examples because it has not > been compiled. > > I know I can build everything at once and it will work, ... I don't understand

Re: [CMake] linking static libs into shared libs on Linux

So maybe the yasm source needs to have a keyword or two added to select PIC addressing mode? Random googling finds suggestions at http://cvs.tortall.net/pipermail/bug-yasm/2011-October/86.html On Wed, Jul 8, 2015 at 10:11 AM, Steve Borho wrote: > On 07/07, Dan Kegel wrote: >> On Tue, Jul 7,

Re: [CMake] Segmentation fault

On 07/08/2015 10:58 AM, Ghyslain Leclerc wrote: > I think I have found a bug in CMake and as suggested in the > Mantis Bug Tracker, I am writing here on the list before > actually filing the bug report in case it’s actually not a bug. > I have also searched in the already filed bugs for a few minut

[CMake] Finding internal libraries

I am trying to build a library along with examples on how to use the library. For simplicity, let's say the structure is CMakeLists.txt src/ CMakeLists.txt foo.c foo.h examples/ CMakeLists.txt ex1/ CMakeLists.txt ex1.c ex2/ CMakeLists.txt ex2.c

Re: [CMake] linking static libs into shared libs on Linux

On 07/07, Dan Kegel wrote: > On Tue, Jul 7, 2015 at 2:25 PM, Steve Borho wrote: > > We're already adding -fPIC to the compile flags for the two object > > libraries. This way one set of objects can be used to output the shared > > library and the static library. So the C++ files are already compil

[CMake] Segmentation fault

Hello, I think I have found a “bug” in CMake and as suggested in the Mantis Bug Tracker, I am writing here on the list before actually filing the bug report in case it’s actually not a bug. I have also searched in the already filed bugs for a few minutes to see if it already exists and it does

Re: [CMake] cmake: Duplicate file name conflict

Thank you Petr! AUTOMOC is the culprit. That pointed me in the right direction. I was able to find this and this . It seems as if it is something that can't be changed due to the design of AUT

Re: [CMake] cmake: Duplicate file name conflict

I can't see anything obviously wrong with your setup. Can you post the error you're getting as well? The only candidate for trouble I can think of is AUTOMOC. I don't have experience with that, but is it possible the name clash comes from AUTOMOC-generated files? Petr On Wed, Jul 8, 2015 at 9:46

Re: [CMake] cmake: Duplicate file name conflict

Hi Peter, Thanks for your quick reply. My file structure is as such someFolder/ library/code/include/*sameName.h* library/code/include/anotherName.h library/code/source/sameName.cpp library/code/source/anotherName.cpp

Re: [CMake] cmake: Duplicate file name conflict

Hi Jan, it'simpossible to answer such questions without seeing your setup. Can you post your CMakeList and your directory structure? Petr On Tue, Jul 7, 2015 at 6:36 PM, Jan Steinke wrote: > Dear all, > I came across a problem, for me it seems that cmake does not allow header > files to be hav