On 8/25/2015 11:34 AM, Parag Chandra wrote:
Hi Philip,
I think I had a similar problem a while back. You basically need to
initialize CMake’s cache values the first time you run it to create a new
build system. So something like this:
cmake -C InitialCacheValues.cmake
And then your InitialCach
CMake does not really support this. At build time CMake scans the
source files and builds the depend list. Since your file is not
actually included it does not end up in the depend list. To add this as
a feature you would have to put the information into DependInfo.cmake
and have cmDependsC.
Hi,
On Wed, Aug 26, 2015 at 3:10 PM, Jakob van Bethlehem <
jsvanbethle...@gmail.com> wrote:
> Hej Andrew,
>
> CMake does never scan source files (as far as I know), as it is not a
> compiler. From your question it almost seem you are making this assumption,
> so I just wanted to make sure to ment
Hi,
You are wrong. CMake, during configuration/generation phase generates
dependencies over C/C++ files.
So, the simple approach to handle dependency between Cpp and h files is to let
CMake handle it:
add_executable (my_exe Main.cpp)
And, that it! By default current source directory is passed
Hej Andrew,
CMake does never scan source files (as far as I know), as it is not a compiler.
From your question it almost seem you are making this assumption, so I just
wanted to make sure to mention at least this.
Then, for your particular issue: two things that come to my mind:
* I’d imagine y
