On 1/29/2014 8:35 AM, Dominik Bernhardt wrote:
I just tested it again with the latest master from today. For my
particular project the configure step with the current master takes
290s. If I only replace the UseQt4.cmake in the master with the
version from 2.8.12.1 the configure time goes down
On 01/29/2014 08:35 AM, Dominik Bernhardt wrote:
I just tested it again with the latest master from today. For my
particular project the configure step with the current master takes
290s. If I only replace the UseQt4.cmake in the master with the
version from 2.8.12.1 the configure time
On 2014-01-29 09:58, Brad King wrote:
I reverted the 'AddVersionToProjectCommand' topic from 'next'
and replaced it with a 'project-version-variables' topic that
adds a policy:
Help: Format project command and variable documentation
On 01/29/2014 10:33 AM, Matthew Woehlke wrote:
Can one use project(VERSION) and later set the policy to OLD to get the
old, don't-unset-the-variables behavior from that point onwards?
Yes. A subproject that has not been updated to understand the
policy would normally run
On Wednesday, January 29, 2014 02:35:53 PM Dominik Bernhardt wrote:
-Urspruengliche Nachricht-
Von: Clinton Stimpson [mailto:clin...@elemtech.com]
Gesendet: Dienstag, 21. Januar 2014 16:10
An: cmake-developers@cmake.org
Cc: Bill Hoffman; Dominik Bernhardt
Betreff: Re:
-Urspruengliche Nachricht-
Von: Clinton Stimpson [mailto:clin...@elemtech.com]
Gesendet: Mittwoch, 29. Januar 2014 17:07
An: cmake-developers@cmake.org
Cc: Dominik Bernhardt
Betreff: Re: [cmake-developers] WG: [CMake] CMake 2.8.12.201401116
is much slower than 2.8.12.1
[...]
Can
On 1/29/2014 11:54 AM, Dominik Bernhardt wrote:
Unfortunately it did not help. Approximately same results as before.
Have you run --trace to see why UseQt4 is being parsed so many times?
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
I noticed in the git history that the kitware robot changed the
documentation in the source files to something with :: characters between
paragraphs.
It also seemed to add them between the paragraphs of the same descriptions:
# CUDA_WRAP_SRCS ( cuda_target format generated_files file0 file1
On Jan 24, 2014, at 3:25 PM, Steve Wilson ste...@wolfram.com wrote:
The first item I would like to see merged back to the project is issue 9974
in the Mantis tracker (CMake should support custom commands that can vary by
configuration). I am the author of the original set of patches
In working with my older build system with CMake from the master branch, I
quickly ran into policy CMP0043: Ignore COMPILE_DEFINITIONS_Config
properties. My build system makes heavy use of the
COMPILE_DEFINITIONS_Config, COMPILE_FLAGS_Config, LINK_FLAGS_Config
paradigm for setting
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14724
==
Reported By:Craig Scott
Assigned To:
Re-including the list.
You could also find more details reading the documentation of the if
command. See http://www.cmake.org/cmake/help/git-master/command/if.html
On Wed, Jan 29, 2014 at 7:40 PM, Rob McDonald rob.a.mcdon...@gmail.comwrote:
Yep, that does it for me. Sneaky...
Rob
On
12 matches
Mail list logo