Re: [CMake] How to get generated dependencies

2016-01-13 Thread J Decker
Or reorganize your project so your includes aren't all scattered and just INSTALL(DIRECTORY include ) On Wed, Jan 13, 2016 at 12:00 PM, Tom Kacvinsky wrote: > Should have read the docs before I asked that last question: > file(STRINGS ...) is what I want > > On Wed, Jan 13, 2016 at 2:59 PM, Tom

Re: [CMake] How to get generated dependencies

2016-01-13 Thread Tom Kacvinsky
Should have read the docs before I asked that last question: file(STRINGS ...) is what I want On Wed, Jan 13, 2016 at 2:59 PM, Tom Kacvinsky wrote: > I suppose what I could do is get the target properties for the > compiler flags (will this include compiler defines and include > directories?), ad

Re: [CMake] How to get generated dependencies

2016-01-13 Thread Tom Kacvinsky
I suppose what I could do is get the target properties for the compiler flags (will this include compiler defines and include directories?), add -MDD -c (using gcc, so those are the options I want) to the compiler flags and make a custom command to generate the file, then post process it to get the

Re: [CMake] How to get generated dependencies

2016-01-13 Thread J Decker
On Wed, Jan 13, 2016 at 11:31 AM, j s wrote: > From what I remember from the mailing list a long time ago, CMake has its > own dependency generator independent of the CPP. > it does; but not for all generators > > On 1/13/16 1:20 PM, Tom Kacvinsky wrote: >> >> On Wed, Jan 13, 2016 at 2:09 PM, J De

Re: [CMake] How to get generated dependencies

2016-01-13 Thread j s
From what I remember from the mailing list a long time ago, CMake has its own dependency generator independent of the CPP. On 1/13/16 1:20 PM, Tom Kacvinsky wrote: On Wed, Jan 13, 2016 at 2:09 PM, J Decker wrote: The short answer is 'no'. I see depends.internal was generated with the gcc (i

Re: [CMake] How to get generated dependencies

2016-01-13 Thread Tom Kacvinsky
On Wed, Jan 13, 2016 at 2:09 PM, J Decker wrote: > The short answer is 'no'. I see depends.internal was generated with the gcc (in my case) option -MD (or perhaps -MDD). Ss cmake knows how to do this. Question: is this at build time or Makefile generation time? If the latter, it would be nice

Re: [CMake] How to get generated dependencies

2016-01-13 Thread J Decker
The short answer is 'no'. On Wed, Jan 13, 2016 at 10:26 AM, Tom Kacvinsky wrote: > On Tue, Jan 12, 2016 at 9:58 AM, Tom Kacvinsky > wrote: >> Is there a way of invoking cmake to get the list of non-system header >> dependencies, like invoking gcc with -MMD? I need to find out the >> list of non

Re: [CMake] How to get generated dependencies

2016-01-13 Thread Tom Kacvinsky
On Tue, Jan 12, 2016 at 9:58 AM, Tom Kacvinsky wrote: > Is there a way of invoking cmake to get the list of non-system header > dependencies, like invoking gcc with -MMD? I need to find out the > list of non-system header dependencies and I know cmake has a way of > doing this, I just need to kno

[CMake] How to get generated dependencies

2016-01-12 Thread Tom Kacvinsky
Is there a way of invoking cmake to get the list of non-system header dependencies, like invoking gcc with -MMD? I need to find out the list of non-system header dependencies and I know cmake has a way of doing this, I just need to know if there is command I can put in the CMakeLists.txt file to g