public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: Brijesh Singh <brijesh.singh@amd.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] EDK2 CI build error "Uncrustify Coding Standard"
Date: Wed, 8 Dec 2021 11:15:29 -0500	[thread overview]
Message-ID: <d0600c8c-759e-3162-7f28-4590cd9399ed@linux.microsoft.com> (raw)
In-Reply-To: <18d2cc3b-9b31-3d8a-29b4-a0f888fd9afc@amd.com>

That's correct. I recommend using the "stuart_update -c 
.pytool/CISettings.py" command so the proper version will automatically 
get brought down into your local workspace.

Thanks,
Michael

On 12/8/2021 11:10 AM, Brijesh Singh wrote:
> 
> 
> On 12/8/21 8:39 AM, Brijesh Singh wrote:
> ...
> 
>>> OvmfPkg Example:
>>>
>>>      git ls-files OvmfPkg/*.c OvmfPkg/*.h :!BaseTools/* | 
>>> .pytool\Plugin\UncrustifyCheck\mu-uncrustify-release_extdep\Windows-x86\uncrustify.exe 
>>> -c .pytool\Plugin\UncrustifyCheck\uncrustify.cfg -F - --replace 
>>> --no-backup --if-changed
>>>
>>>
>>
>> Thanks for the detail, I just did a pull and now I see the uncrustify 
>> cfg files. I followed your above command on my Ubuntu desktop and 
>> getting the below unknown symbol, is this a known issue ?
>>
>>
>> brijesh@sbrijesh-desktop:~/workdir/snp-edk2$ git ls-files 
>> OvmfPkg/Sec/AmdSev.c | uncrustify -c 
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg -F - --replace 
>> --no-backup --if-changed
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:73: unknown symbol 
>> 'nl_func_call_args_multi_line_ignore_closures'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:79: unknown symbol 
>> 'indent_func_call_edk2_style'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:120: unknown symbol 
>> 'sp_do_brace_open'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:134: unknown symbol 
>> 'sp_before_vardef_square'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:178: unknown symbol 
>> 'sp_brace_close_while'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:184: unknown symbol 
>> 'sp_before_square_asm_block'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:205: unknown symbol 
>> 'sp_while_paren_open'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:229: unknown symbol 
>> 'indent_func_def_param_paren_pos_threshold'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:270: unknown symbol 
>> 'align_edk2_style'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:323: unknown symbol 
>> 'cmt_align_doxygen_javadoc_tags'
>> .pytool/Plugin/UncrustifyCheck/uncrustify.cfg:406: unknown symbol 
>> 'nl_before_whole_file_ifdef'
>> Parsing: OvmfPkg/Sec/AmdSev.c as language C
>> brijesh@sbrijesh-desktop:~/workdir/snp-edk2$
>> brijesh@sbrijesh-desktop:~/workdir/snp-edk2$ uncrustify --version
>> Uncrustify-0.69.0_f
>>
>> I did submitted PR after above uncurstify run but the CI still didn't 
>> like it. Do we need to have specific version of uncrustify ?
>>
> 
> Reading through the "Add Uncrustify formatting overview" email it seems 
> we need to use a edk2 forked  version of uncrustify [1]. With this now I 
> dont get any error.
> 
> [1] 
> https://dev.azure.com/projectmu/Uncrustify/_packaging?_a=package&feed=mu_uncrustify&package=mu-uncrustify-release&version=73.0.3&protocolType=NuGet 
> 
> 
> 
> 
> thanks

  reply	other threads:[~2021-12-08 16:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:52 EDK2 CI build error "Uncrustify Coding Standard" Brijesh Singh
2021-12-07 20:49 ` [edk2-devel] " Michael Kubacki
2021-12-07 21:02   ` Michael D Kinney
2021-12-08 14:39     ` Brijesh Singh
2021-12-08 16:10       ` Brijesh Singh
2021-12-08 16:15         ` Michael Kubacki [this message]
2022-04-05  5:57           ` Ashish Kalra
2022-04-05  6:09             ` Ashish Kalra
2022-04-05 14:40               ` Michael Kubacki
2022-04-05 14:42                 ` Michael Kubacki
2022-04-05 15:00               ` Rebecca Cran
2022-04-05 15:21                 ` Michael D Kinney

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=d0600c8c-759e-3162-7f28-4590cd9399ed@linux.microsoft.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