From: "丰立波 via groups.io" <lbfeng=kunluntech.com.cn@groups.io>
To: radio-fan <radio-fan@mail.ru>
Cc: devel <devel@edk2.groups.io>
Subject: Re: [edk2-devel] buiding Uefi Universal Payload failed
Date: Sat, 29 Mar 2025 10:50:09 +0800 (GMT+08:00) [thread overview]
Message-ID: <ALsA7gD2Lr4iOzFrTIwx6Koc.3.1743216609639.Hmail.lbfeng@kunluntech.com.cn> (raw)
In-Reply-To: <31135.1742285957898975336@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Hello, Stepan,
I can build the payload with your approach.
I think the commint of 71188e90638cac8d5228e89b0fb5809783058946 solves the problem:
BaseTools: Add BUILDRULEFAMILY for CLANGDWARF
Commit c6f47e6 removed BUILDRULEFAMILY for CLANGDWARF. Adding
CLANGDWARF back as a BUILDRULEFAMILY to match CLANGPDB.
Add CLANGDWARF specific build rules - based on GCC, and remove steps
not required for CLANGDWARF.
Remove following irrelevant steps and logs:
...
"objcopy not needed ..."
"--strip-unneded ..."
"--add-gnu-debuglink ..."
...
Best Regards
Feng Libo
Original:
From:Stepan via groups.io<radio-fan=mail.ru@groups.io>Date:2025-03-18 16:19:17(中国 (GMT+08:00))To:丰立波<lbfeng@kunluntech.com.cn> , devel<devel@edk2.groups.io>Cc:Subject:[edk2-devel] buiding Uefi Universal Payload failedHello Feng Libo,
I found this bug, when i update EDK2 sources. You should remove directories Build, Conf and BaseTools. Then restore the source code of the BaseTools (git reset --hard HEAD). Then rebuild tools by make -c BaseTools/ and update environment by source edksetup.sh . After this You can apply settings for the target in Conf/target.txt .
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121232): https://edk2.groups.io/g/devel/message/121232
Mute This Topic: https://groups.io/mt/111636381/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 5814 bytes --]
prev parent reply other threads:[~2025-03-29 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 8:43 [edk2-devel] buiding Uefi Universal Payload failed 丰立波 via groups.io
2025-03-12 5:21 ` Stepan via groups.io
2025-03-13 8:42 ` 丰立波 via groups.io
2025-03-13 10:35 ` Alireza Banejad via groups.io
[not found] ` <182C50338DEC62BE.19915@groups.io>
2025-03-13 9:26 ` 丰立波 via groups.io
2025-03-13 10:53 ` Stepan via groups.io
2025-03-13 12:05 ` Ard Biesheuvel via groups.io
2025-03-18 8:19 ` Stepan via groups.io
2025-03-18 8:20 ` Stepan via groups.io
2025-03-29 2:50 ` 丰立波 via groups.io [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=ALsA7gD2Lr4iOzFrTIwx6Koc.3.1743216609639.Hmail.lbfeng@kunluntech.com.cn \
--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