On 8/14/2014 11:26 AM, Nagger wrote:
So ZERO_CHECK is 34 times faster. Why shouldn't I take advantage of that.
If CMake does not need to re-run, then ZERO_CHECK will always be faster
than cmake build_dir. cmake build_dir will run a full configure and
generate no matter what. That said, a cm
Am 14.08.2014 16:31, schrieb David Cole:
We have a fairly large project with about 400 targets.
$ cmake %builddir%
-> takes about 5 minutes for a No-op
$ cmake --build %builddir% --target ZERO_CHECK
-> takes 20 seconds for No-op
This is the problem.
"cmake %builddir%" should be as fas
We have a fairly large project with about 400 targets.
$ cmake %builddir%
-> takes about 5 minutes for a No-op
$ cmake --build %builddir% --target ZERO_CHECK
-> takes 20 seconds for No-op
This is the problem.
"cmake %builddir%" should be as fast as possible for a no-op... If it's
not,
Am 14.08.2014 08:13, schrieb Hendrik Sattler:
On 13. August 2014 21:40:34 MESZ, Nagger wrote:
But what I really miss is an "--update" option for CMake which is doing
all the work (updating if possible, configuring if necessary)
internally. It would use the implementation of 'cmake --build' to
On 13. August 2014 21:40:34 MESZ, Nagger wrote:
>But what I really miss is an "--update" option for CMake which is doing
>
>all the work (updating if possible, configuring if necessary)
>internally. It would use the implementation of 'cmake --build' to
>trigger a re-configure and if that is no
Am 13.08.2014 21:59, schrieb Paul Smith:
On Wed, 2014-08-13 at 21:40 +0200, Nagger wrote:
Does anyone already came up with a good solution? Isn't this a common
problem?
I'm not sure about the other generators, but the makefile generator has
this built-in; that is, if the makefiles detect that
On Wed, 2014-08-13 at 21:40 +0200, Nagger wrote:
> Does anyone already came up with a good solution? Isn't this a common
> problem?
I'm not sure about the other generators, but the makefile generator has
this built-in; that is, if the makefiles detect that a cmake file has
changed it will re-run
Hello,
For our Continuous Integration tests we need fast incremental builds
(only build what has changed).
This also includes that CMake only has to run if necessary (some
CMakeLists.txt changed).
It seems there is no beautiful/portable/generator-independent way to do
this?!
Fortunately we m
