From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2563 invoked by alias); 21 Aug 2011 20:41:28 -0000 Received: (qmail 2554 invoked by uid 22791); 21 Aug 2011 20:41:28 -0000 X-SWARE-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from tetra.codeconfidence.com (HELO tetra.codeconfidence.com) (94.229.66.225) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 21 Aug 2011 20:41:11 +0000 Received: from cog.dallaway.org.uk (cpc1-cmbg10-0-0-cust34.5-4.cable.virginmedia.com [81.102.132.35]) by tetra.codeconfidence.com (Postfix) with ESMTP id B9618234C700; Sun, 21 Aug 2011 21:41:09 +0100 (BST) Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id p7LKf8UC030529; Sun, 21 Aug 2011 21:41:09 +0100 Message-ID: <4E516D64.8000403@dallaway.org.uk> Date: Sun, 21 Aug 2011 20:41:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.24 (X11/20110622) MIME-Version: 1.0 To: Sergei Gavrikov CC: eCos Developers Subject: Re: Verbose modes for eCos makefiles References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2011-08/txt/msg00005.txt.bz2 Hi Sergei Sergei Gavrikov wrote: > It was added a few checks for "V" variable (a verbose level) in eCos > ``rules.mak`` file and the level of the verbosity is set in a top most > eCos ``makefile`` (which is auto-generated). The level of verbosity can > be set from a command line as ``make V=x`` where "x" can be set to 0, 1, > or 2) > > V=0 - silent build (it is equal to a call ``make --silent``) > V=1 - "semi-silence", when ``make`` outputs a kind of work is > doing now > V=2 - full output (it is equal to "old" call of ``make``) > > Default level is 1 (semi-silence). IMHO, it is right value and it is no > need to type ``make V=1`` every time. > > Pros (V=1): > > - He/she will be know what is running. > - He/she will be know/learn an order the build process. > - He/she will see any warnings and possible they will sent us the > patches to fix it :-) > > % make tests > ... > CC strtoul.c > LINK strtoul > CC memchr.c > /home/sg/repo/ecos-hg/packages/language/c/libc/string/current/tests/memchr.c: In function ‘main’: > /home/sg/repo/ecos-hg/packages/language/c/libc/string/current/tests/memchr.c:107: warning: assignment discards qualifiers from pointer target type > LINK memchr > ... I can appreciate that the "semi-silent" output you are proposing makes warning messages stand out more clearly, but this appears to be the only benefit. The existing output already indicates what is running and the order of the build process. Have I missed something? > Cons: > > - It is needed to re-built ``ecosconfig`` to get it working. > > NOTE: Only a few lines were added to only one source > host/tools/configtool/common/common/build.cxx > > - Very few people work with command-line and they need to know about > V=x (V=2). > - eCos ConfigTool (may be "semi-silence" is odd for it, not tested). I would also be concerned about the processing overhead on Cygwin hosts and the possiblility of unexpected output when using multiple eCos repositories or older eCos host tools. Is your proposal based on another build system you have used? John Dallaway eCos maintainer http://www.dallaway.org.uk/john