[vtk-developers] Lack of feedback during cache building

Elvis Stansvik elvis.stansvik at orexplore.com
Fri Jan 11 18:21:34 EST 2019


Den fre 11 jan. 2019 kl 20:01 skrev Bill Lorensen <bill.lorensen at gmail.com>:
>
> I like to see what modules might be excluded, etc. I'd like to see something.
>
> Is this the consensus?

I would also like something like that, perhaps something like this:
https://gist.github.com/estan/db8a9d5ea9e1354822484e9872204e96

Wouldn't have to be always on, but with an option.

I challenge anyone to write a printout like that in CMake :)

Elvis

>
> On Fri, Jan 11, 2019, 10:54 AM Ben Boeckel <ben.boeckel at kitware.com wrote:
>>
>> On Fri, Jan 11, 2019 at 10:31:32 -0800, Bill Lorensen wrote:
>> > If the cache is rebuilt, I do not get and feedback. Just
>> > Configuring done
>> >
>> > How to get the feedback we used to get?
>>
>> What benefit did you derive from it? I always saw it as a wall of noise,
>> personally since it was unconditional and larger than a single screen
>> anyways.
>>
>> I guess, what output should we be generating? For each bit: Should it be
>> unconditional? If not, should it be on by default?
>>
>> --Ben
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>
> Follow this link to subscribe/unsubscribe:
> https://vtk.org/mailman/listinfo/vtk-developers
>


More information about the vtk-developers mailing list