From: "wang xiaofeng" <winggundum82@163.com>
To: "Andrew Fish" <afish@apple.com>
Cc: edk2-devel <edk2-devel@lists.01.org>
Subject: Re: How to build commonlib of Basetools in x64 mode
Date: Fri, 23 Dec 2016 12:15:46 +0800 (CST) [thread overview]
Message-ID: <70539f18.53f1.15929e451fd.Coremail.winggundum82@163.com> (raw)
In-Reply-To: <CE7102C6-78B7-4631-8641-AF27FFAB52FE@apple.com>
HI Fish,
Thanks for your answer. Actually I am not trying to build base tools . I am writing a windows console tool and want to reuse some code of base tools common library, All the changes will be in my platform packages, Due to some history reason , my own tool is treating UINTN as x64 mode, so will it possible to build common.lib in X64 mode?
Thanks in advance!
At 2016-12-23 11:59:38, "Andrew Fish" <afish@apple.com> wrote:
>The base tools width could be OS Specific so you should not depend on it. In other words it has nothing to do with your ROM. You should code tools to exact sizes, and only use UINTN if you don't care about size.
>
>Sent from my iPhone
>
>> On Dec 22, 2016, at 7:35 PM, wang xiaofeng <winggundum82@163.com> wrote:
>>
>> Hi Base tool owners,
>> I tried to build commonlib in basetools . And use the library file in my own application tool . I just found the commonlib is build in IA32 mode ,this means UINTN is 4 byte in the output lib. I expect to build a X64 mode Common.lib ,can you help me?
>> Or base tools can only run in IA32 mode?
>> _______________________________________________
>> 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
next prev parent reply other threads:[~2016-12-23 4:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 18:25 [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables evan.lloyd
2016-12-19 9:48 ` Ni, Ruiyu
2016-12-19 15:57 ` Evan Lloyd
2016-12-19 18:01 ` Carsey, Jaben
2016-12-20 2:59 ` Ni, Ruiyu
2016-12-20 3:56 ` Carsey, Jaben
2016-12-20 4:49 ` Yao, Jiewen
2016-12-20 5:18 ` Ni, Ruiyu
2016-12-20 5:54 ` Yao, Jiewen
2016-12-20 13:20 ` Evan Lloyd
2016-12-20 16:35 ` Yao, Jiewen
2016-12-22 18:25 ` Evan Lloyd
2016-12-23 1:31 ` Yao, Jiewen
2017-01-13 8:10 ` Bhupesh SHARMA
2017-01-13 13:26 ` Yao, Jiewen
2016-12-23 3:35 ` How to build commonlib of Basetools in x64 mode wang xiaofeng
[not found] ` <CE7102C6-78B7-4631-8641-AF27FFAB52FE@apple.com>
2016-12-23 4:15 ` wang xiaofeng [this message]
[not found] ` <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C3866@shsmsx102.ccr.corp.intel.com>
2016-12-23 4:54 ` Andrew Fish
2016-12-23 5:02 ` wang xiaofeng
2016-12-23 5:09 ` Gao, Liming
2016-12-20 12:22 ` [PATCH] ShellPkg: Add acpiview tool to dump ACPI tables Evan Lloyd
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=70539f18.53f1.15929e451fd.Coremail.winggundum82@163.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