[x264-devel] [PATCH 0/2] Silent build rules

BugMaster BugMaster at narod.ru
Sat Apr 5 07:39:49 CEST 2014


On Fri, 4 Apr 2014 14:47:21 -0400, Stephen Hutchinson wrote:
> On Fri, Apr 4, 2014 at 1:55 PM, BugMaster <BugMaster at narod.ru> wrote:
>> Hi. I don't understand what for you are trying to silence anything?
>> What is reason for such use case? Because I can't justify such
>> complication of configure/make scripts for some abstract no real
>> reason. So imho it is not needed (x264 is not so big project as ffmpeg
>> to silent something in build process).
>>

> The practical reason is that it makes warnings easier to locate
> in the build output.  Without the silencing, the output warnings and the
> actual compilation commands just blend into a large wall of text in
> the Terminal.

imho redirecting stdout or stderr for make is much easier than
changing (complicating) configure/makefile.

 `make -j8 2>warnings.txt` if you want to see progress of compilation
 and latter to look for the warnings/errors.
 `make -j8 >/dev/null` [or `make -j8 >NUL` at Windows] if you want to
 see only warnings/errors in terminal.

I prefer to use first variant because I can look at warnings latter
and don't need to care about terminal width or height and be sure non
of the warnings will be missed due not enough space in terminal.



More information about the x264-devel mailing list