public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ken Taylor" <Ken_Taylor@phoenix.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] VS2019 and AARCH64 with current EDKII mainline code.
Date: Tue, 19 Mar 2024 21:12:04 +0000	[thread overview]
Message-ID: <MN0P223MB048597ADD35D2F110100DE7FFA2C2@MN0P223MB0485.NAMP223.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Hi all,

I've been trying to build the latest 2023 release of EDKII with AARCH64 using VS2019, and I'm encountering an issue with line 51 of MdePkg\Library\BaseLib\AArch64\SetJumpLongJump.asm.

Specifically, there's no EXTERN for InternalAssertJumpBuffer and the 64 bit ARM cross assembler that comes with VS2019 does not support /D or -D so there's no way to set a flag that properly defines MDEPKG_NDEBUG.  -PreDefine "MDEPKG_NDEBUG SETx blah" doesn't work either, because it doesn't declare MDEPKG_NDEBUG in a context that the assembler's preprocessor recognizes.

How is this supposed to work, exactly?  For now, I'm using my own version of BaseLib, so I can remove that code block from SetJumpLongJump.asm, or add the EXTERN, but that's far from ideal since I'd like to avoid maintaining my own copy of BaseLib just to fix a single build error.

Regards,
-Ken Taylor


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116908): https://edk2.groups.io/g/devel/message/116908
Mute This Topic: https://groups.io/mt/105033123/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: 3677 bytes --]

             reply	other threads:[~2024-03-19 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 21:12 Ken Taylor [this message]
2024-03-20  3:48 ` [edk2-devel] VS2019 and AARCH64 with current EDKII mainline code Adam Liu

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=MN0P223MB048597ADD35D2F110100DE7FFA2C2@MN0P223MB0485.NAMP223.PROD.OUTLOOK.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