On 11/26/2013 08:20 AM, Peter Kümmel wrote:
Will be fixed in QtCreator 3.0.
Thank you for the fix!
Nils
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
ht
On 11.11.2013 18:33, Matthew Woehlke wrote:
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 ed
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
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
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
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
