public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ryan Harkin <ryan.harkin@linaro.org>
To: Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: Andrew Fish <afish@apple.com>, edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: How to silence a build?
Date: Tue, 13 Dec 2016 09:46:13 +0000	[thread overview]
Message-ID: <CAD0U-h+FrHeh5BiVpJhZA39G+UGevtA70rUUHMdTfXRrhFzDsA@mail.gmail.com> (raw)
In-Reply-To: <CAN9vWDLLDLrgJy7ZCiPsrFnA15tLEg=58U3fcFE68M=E6pqb-w@mail.gmail.com>

Thanks both.

I think Andrew's idea is what I'm really looking for.  But in the
meantime, adding "-s" as Michael suggested is working quite well.

On 12 December 2016 at 18:58, Michael Zimmermann
<sigmaepsilon92@gmail.com> wrote:
> these build command options are probably what you want:
>
>   -s, --silent          Make use of silent mode of (n)make.
>   -q, --quiet           Disable all messages except FATAL ERRORS.
>   -v, --verbose         Turn on verbose output with informational messages
>                         printed, including library instances selected, final
>                         dependency expression, and warning messages, etc.
>   -d DEBUG, --debug=DEBUG
>                         Enable debug messages at specified level.
>
> Thanks,
> Michael
>
> On Mon, Dec 12, 2016 at 7:34 PM, Andrew Fish <afish@apple.com> wrote:
>>
>>> On Dec 12, 2016, at 10:27 AM, Ryan Harkin <ryan.harkin@linaro.org> wrote:
>>>
>>> Hello all,
>>>
>>> Perhaps someone here can save me trying to decrypt the EDK2 build system.
>>>
>>> When I build EDK2, I get lots of output like this single line
>>> generated for compiling a single source file:
>>>
>>> "/linaro/extra-data/ci/workspace-lsk/tools/gcc/gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc"
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/ArmPlatformPkg/ArmVExpressPkg/Include
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/ArmPlatformPkg/ArmVExpressPkg/Include/Platform/RTSM
>>> -g -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-array-bounds
>>> -ffunction-sections -fdata-sections -include AutoGen.h -fno-common
>>> -DSTRING_ARRAY_NAME=UiAppStrings -g -Os -fshort-wchar
>>> -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -include
>>> AutoGen.h -fno-common -mlittle-endian -fno-short-enums -fverbose-asm
>>> -funsigned-char -ffunction-sections -fdata-sections -fno-builtin
>>> -Wno-address -fno-asynchronous-unwind-tables -save-temps -O0
>>> -mcmodel=small -c -o
>>> /linaro/extra-data/ci/workspace-lsk/uefi/edk2/Build/ArmVExpress-FVP-AArch64/DEBUG_GCC5/AARCH64/MdeModulePkg/Application/UiApp/UiApp/OUTPUT/./String.obj
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdeModulePkg/Application/UiApp
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/Build/ArmVExpress-FVP-AArch64/DEBUG_GCC5/AARCH64/MdeModulePkg/Application/UiApp/UiApp/DEBUG
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdePkg
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdePkg/Include
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdePkg/Include/AArch64
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdeModulePkg
>>> -I/linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdeModulePkg/Include
>>> /linaro/extra-data/ci/workspace-lsk/uefi/edk2/MdeModulePkg/Application/UiApp/String.c
>>>
>>> When I build the linux kernel, I see output like this:
>>>
>>>  CC      kernel/nsproxy.o
>>>  OBJCOPY arch/arm64/kernel/efi-entry.stub.o
>>>
>>> Is there an option to make EDK2 do something like this?
>>>
>>> Or can someone point me where I might look so I can think about
>>> implementing it?
>>
>> Ryan,
>>
>> The content of Conf/build_rule.txt is used to construct the makefiles. The rules under <Command.GCC> will get translated into the generated makefiles. If you prepend an @ that makefile line should no longer echo.
>>
>> The Conf/build_rule.txt will get copied from the BaseTools/Conf//build_rule.template if it does not exist when you run edksetup.sh.
>>
>> You can always add an @print line to print out anything you want.
>>
>> Thanks,
>>
>> Andrew Fish
>>
>>
>>>  I've had a look around and wasn't able to work out
>>> what was generating the output.  I guess that means my chances of
>>> changing the behaviour are slim too...
>>>
>>> Thanks,
>>> Ryan.
>>> _______________________________________________
>>> edk2-devel mailing list
>>> edk2-devel@lists.01.org
>>> https://lists.01.org/mailman/listinfo/edk2-devel
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2016-12-13  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 18:27 How to silence a build? Ryan Harkin
2016-12-12 18:34 ` Andrew Fish
2016-12-12 18:58   ` Michael Zimmermann
2016-12-13  9:46     ` Ryan Harkin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAD0U-h+FrHeh5BiVpJhZA39G+UGevtA70rUUHMdTfXRrhFzDsA@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox