[CMake] How to include public-headers of dependent targets first, before arguments in target_include_directories()

I want to cross-compile cairo in many systems, and cairo depend on zlib, libpng and pixman, optionally search for freetype and fontconfig. I got sources of zlib, libpng and pixman, and use cmake to compile and link them. But when compile cairo, I got following flags by cmake: C_INCLUDES = -I/Us

[CMake] (no subject)

http://bit.ly/1TOTr0m?675=bebenuci&991&lenuk==33306881 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visi

Re: [CMake] Building a tool immediately so it can be used later in same CMake run

Am 14.04.2016 um 14:17 schrieb Craig Scott: Re-using the same build directory is a key part of the technique to avoid having to build the same thing twice. A vague idea: Use two different CMAKE_BINARY_DIRs but let the two mycompdir-targets use the same binary subdirectory. (By using the 2nd p

Re: [CMake] c++11 feature and cmake feature name mapping

I don't think CMake can yet detect features of the standard library implementation, only features of the language. One compiler may support more features than another compiler which supports more of the standard library, and in some cases the same compiler can support two or more different standard

Re: [CMake] Building a tool immediately so it can be used later in same CMake run

Sorry, forgot to follow up on this response. Re-using the same build directory is a key part of the technique to avoid having to build the same thing twice. So far, the only real problem I've seen is that the Xcode generator is potentially less suited to this arrangement in that it seems very hard

Re: [CMake] c++11 feature and cmake feature name mapping

There are pros and cons to specifying individual compiler features compared to just specifying a C++ standard overall. It depends somewhat on what else you have to link in. For example, if you link to a third party library built with C++11 settings, you will have to link in that same library to avo

Re: [CMake] How to deal with generated source files (w/ dependency tracking) for globs

It's not quite your situation, but it may have some common elements and the general idea may get you thinking about what might work for you. This question/answer I asked this list about last week: http://stackoverflow.com/q/36084785/1938798 We've been using this approach with success on all the p

[CMake] c++11 feature and cmake feature name mapping

Hi, I know we should use [target_compile_features][1] to enable c++11 features in cmake. And I also found the [descriptions][2] about the features. In my code I used the `random_device`, `default_random_engine` and `uniform_int_distribution` which are a new features, but I could not find a matchi

Re: [CMake] How to deal with generated source files (w/ dependency tracking) for globs

On 4/6/16, iosif neitzke wrote: > I think it depends on when you want the output files from Nim > generated and which files are the most frequently developed. > If it is usually a one-time generation per clean development session, > the simplest case, where the *.NIM source files are not the files