Re: [cmake-developers] Review request: set_emptyvar_PARENT_SCOPE

2013-11-11 Thread Matthew Woehlke
On 2013-11-11 17:33, Daniele E. Domenichelli wrote: On 11/11/13 17:52, Matthew Woehlke wrote: On 2013-11-11 05:13, Daniele E. Domenichelli wrote: WCTS, how does one now unset a variable in parent scope? I recall some time back there was talk of adding PARENT_SCOPE to unset(). If set() can no lo

Re: [cmake-developers] Review request: set_emptyvar_PARENT_SCOPE

2013-11-11 Thread Daniele E. Domenichelli
On 11/11/13 17:52, Matthew Woehlke wrote: > On 2013-11-11 05:13, Daniele E. Domenichelli wrote: > WCTS, how does one now unset a variable in parent scope? > > I recall some time back there was talk of adding PARENT_SCOPE to > unset(). If set() can no longer be used for this purpose, maybe unset()

Re: [cmake-developers] Ninja jumping progress indicator

2013-11-11 Thread Matthew Woehlke
On 2013-11-11 12:17, Nils Gladitz wrote: On 11.11.2013 17:38, Matthew Woehlke wrote: What else can you do? Until you re-run CMake, there is no way to know how many edges need to be executed. Even if ninja were to show the maximum possible number of edges, that could be too small e.g. because you

Re: [cmake-developers] Ninja jumping progress indicator

2013-11-11 Thread Nils Gladitz
On 11.11.2013 17:38, Matthew Woehlke wrote: What else can you do? Until you re-run CMake, there is no way to know how many edges need to be executed. Even if ninja were to show the maximum possible number of edges, that could be too small e.g. because you've added a bunch of new targets since t

Re: [cmake-developers] Review request: set_emptyvar_PARENT_SCOPE

2013-11-11 Thread Matthew Woehlke
On 2013-11-11 05:13, Daniele E. Domenichelli wrote: I've pushed a patch to the set_emptyvar_PARENT_SCOPE topic. This patch introduces a new policy (CMP0040) to control the behaviour of set(var "" PARENT_SCOPE) the OLD behaviour is to unset the "var" variable in the parent scope the NEW beh

Re: [cmake-developers] Ninja jumping progress indicator

2013-11-11 Thread Matthew Woehlke
On 2013-11-11 03:15, Nils Gladitz wrote: Could output of the ninja progress indicator be omitted for when it reruns cmake somehow? It outputs 1/1 and then goes on to report the "actual" progress e.g. 1/916 ... What else can you do? Until you re-run CMake, there is no way to know how many edges

[cmake-developers] [CMake 0014559]: 0013084 fix has no backwards compatibility

2013-11-11 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=14559 == Reported By:Derek Chow Assigned To: =

[cmake-developers] [CMake 0014558]: configure step for 'ves-android'

2013-11-11 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14558 == Reported By:rahulchavan Assigned To:

[cmake-developers] [CMake 0014555]: Add ability to INSTALL(CODE|SCRIPT ...) that is always executed at install time regardless of component being installed.

2013-11-11 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=14555 == Reported By:Tim Patterson Assigned To:

[cmake-developers] Review request: set_emptyvar_PARENT_SCOPE

2013-11-11 Thread Daniele E. Domenichelli
Hello, Following this thread: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/8546 I've pushed a patch to the set_emptyvar_PARENT_SCOPE topic. This patch introduces a new policy (CMP0040) to control the behaviour of set(var "" PARENT_SCOPE) the OLD behaviour is to unset th

[cmake-developers] Ninja jumping progress indicator

2013-11-11 Thread Nils Gladitz
Could output of the ninja progress indicator be omitted for when it reruns cmake somehow? It outputs 1/1 and then goes on to report the "actual" progress e.g. 1/916 ... The initial 1/1 confuses QtCreator which does not allow for the progress indicator to jump around this way: https://bugr