[CMake] Less Noisy Makefiles?

Campbell Barton ideasman42 at gmail.com
Sat Oct 9 19:46:02 EDT 2010


On Fri, Oct 8, 2010 at 5:16 AM, Campbell Barton <ideasman42 at gmail.com> wrote:
> On Thu, Oct 7, 2010 at 9:55 PM, David Cole <david.cole at kitware.com> wrote:
>> On Thu, Oct 7, 2010 at 5:34 PM, Campbell Barton <ideasman42 at gmail.com>
>> wrote:
>>>
>>> On Thu, Oct 7, 2010 at 8:48 PM, Campbell Barton <ideasman42 at gmail.com>
>>> wrote:
>>> > On Thu, Oct 7, 2010 at 10:44 AM, Michael Wild <themiwi at gmail.com> wrote:
>>> >>
>>> >> On 7. Oct, 2010, at 11:58 , Campbell Barton wrote:
>>> >>
>>> >>> Hi, I was wondering if this is possible or if it would be acceptable
>>> >>> to disable progress printout.
>>> >>>
>>> >>> At the moment building with only minor changes prints a lot of text
>>> >>> with CMake & Makefiles.
>>> >>>
>>> >>> eg:
>>> >>> [  4%] Built target bf_intern_audaspace
>>> >>> [  4%] Built target bf_intern_string
>>> >>> [  6%] Built target bf_intern_ghost
>>> >>>
>>> >>> full log.
>>> >>> http://www.pasteall.org/16053
>>> >>>
>>> >>> Setting: SET_PROPERTY(GLOBAL PROPERTY RULE_MESSAGES OFF)
>>> >>> is no good because I want to see the lines which are running/building,
>>> >>> just not the progress lines that do nothing (the reverse really).
>>> >>>
>>> >>> I found some messages about this but they only refer to RULE_MESSAGES.
>>> >>>
>>> >>> This may seem silly but its actually one of the reasons we still have
>>> >>> hand written makefiles in our project (which Im trying to get replaced
>>> >>> with cmake).
>>> >>>
>>> >>> Would this be acceptable?
>>> >>>
>>> >>
>>> >> what happens if you run "make VERBOSE=1" or enable
>>> >> CMAKE_VERBOSE_MAKEFILE?
>>> >>
>>> >> Michael
>>> >>
>>> >> --
>>> >> There is always a well-known solution to every human problem -- neat,
>>> >> plausible, and wrong.
>>> >> H. L. Mencken
>>> >
>>> > using verbose makefiles it gives a lot of output even when running a
>>> > build with no changes to any C files.
>>> > http://www.pasteall.org/16061
>>> >
>>> > Im pretty happy with cmake's current output, its just for doing
>>> > rebuilds during development where only a few files change, the
>>> > progress gets in the way of seeing output of the files which do
>>> > rebuild.
>>> >
>>> > So I think it would be good to have a RULE_PROGRESS option, since I
>>> > still want to see RULE_MESSAGES.
>>>
>>> Im using CMake from GIT, and IIRC RULE_MESSAGES used to disable
>>> progress, this link confirms.
>>> http://www.itk.org/Bug/bug_view_advanced_page.php?bug_id=8726
>>>
>>> but at the moment % progress is enabled whatever its set to.
>>>
>>> --
>>> - Campbell
>>> _______________________________________________
>>> 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:
>>> http://www.cmake.org/Wiki/CMake_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.cmake.org/mailman/listinfo/cmake
>>
>> According to the last note in bug #8726, you should run cmake with:
>> -DCMAKE_RULE_MESSAGES=OFF
>> to turn these things off.
>> Have you done that? Or have you only tried the RULE_MESSAGES global
>> property?
>> I have not looked at the code, but the bug says something different than
>> what your email says. -D variables and global properties are 2 different
>> things...
>> If you use -D to set CMAKE_RULE_MESSAGES to OFF does it actually turn them
>> off?
>>
>
> I tried both in latest GIT's cmake, nether turn the progress off
> also looked into the code and from what I can tell there are no checks
> supress progress.
>
> --
> - Campbell
>

Looked into the source and found the reason progress is still being
printed when RULE_MESSAGES is off.
Reported: http://www.cmake.org/Bug/view.php?id=11304

was looking into a progress patch but best this gets resolved first.
-- 
- Campbell


More information about the CMake mailing list