Re: [cmake-developers] [PATCH] FindBoost: Add imported targets

On 18/11/2015 11:27, rle...@codelibre.net wrote: On 11/16/2015 09:26 AM, Florent Castelli wrote: But one there’s one thing that comes to mind. Some compiled libraries have dependencies on other compiled libraries. Don’t you think it would make sense to teach FindBoost about those so we link

[Cmake-commits] CMake branch, next, updated. v3.4.0-1528-gf312371

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via f3123711dfcaea5e1e340e4b0203f23e8e5fc3d9 (commit) via

Re: [CMake] [cmake-developers] Obtaining header file dependencies of a source file manually

On Sun, Nov 29, 2015, 10:47 Dan Liew wrote: Hi, # TL;DR I need a way of determining the header file dependencies of a source file and inform CMake about them. CMake doesn't do this automatically because I'm using custom commands for the compilation step so CMake doesn't do

Re: [cmake-developers] Obtaining header file dependencies of a source file manually

On Sun, Nov 29, 2015, 10:47 Dan Liew wrote: Hi, # TL;DR I need a way of determining the header file dependencies of a source file and inform CMake about them. CMake doesn't do this automatically because I'm using custom commands for the compilation step so CMake doesn't do

[CMake] Obtaining header file dependencies of a source file manually

Hi, # TL;DR I need a way of determining the header file dependencies of a source file and inform CMake about them. CMake doesn't do this automatically because I'm using custom commands for the compilation step so CMake doesn't do it's usual magic of automatically inferring source file header

[CMake] adding gprof to cmake project

I have a project with many libs and one executable. I read this email exchange: https://cmake.org/pipermail/cmake/2009-December/033979.html on adding linker flags but this was from around 2009 and things most likely have changed a lot since then. in my executable my cmakelists.txt looks like

[CMake] Best way to handle application data path for local run vs. installation

Hi! This question bugs me for a long time so I though maybe someone has a solution. I have a project which includes an application and some data for it. An application needs to know path to its data files, so I pass it via compiler definition: ADD_DEFINITIONS(-DDATADIR="...") The problem is that

Re: [CMake] Best way to handle application data path for local run vs. installation

So you want to hard code a location into the executable, but support multiple locations without making multiple executables? These sound like conflicting requirements. Supporting multiple locations seems reasonable, so this suggests that you'll have to change how your application looks for these

[Cmake-commits] CMake branch, master, updated. v3.4.0-608-g31b013b

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20151129) +set(CMake_VERSION_PATCH 20151130) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/