From: "Hiber He" <hiberhe@163.com>
To: devel <devel@edk2.groups.io>, "ray.ni" <ray.ni@intel.com>
Cc: "Feng, Bob C" <bob.c.feng@intel.com>,
戴,曉政 <cloud0907@yahoo.com.tw>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"afish@apple.com" <afish@apple.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] May I become a contributor in EmulatorPkg ?
Date: Mon, 1 Jul 2019 07:05:25 +0800 (GMT+08:00) [thread overview]
Message-ID: <759a7bea.127.16baaa2d136.Coremail.hiberhe@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Hi,
For the second one: Dai already pointed out the problem, a ending slash(\) should be added to the nasm path variable. You can find the following
On 06/30/2019 21:22, Ni, Ray wrote:
Bob,
Any comments?
From:戴,曉政 [mailto:cloud0907@yahoo.com.tw]
Sent: Sunday, June 30, 2019 3:37 PM
To: Justen, Jordan L <jordan.l.justen@intel.com>; afish@apple.com; Ni, Ray <ray.ni@intel.com>
Subject: May I become a contributor in EmulatorPkg ?
Dears,
I live in Taiwan so please forgive my English pool. I download edk2 source code from Github recently and I encounter two build error when I build EmulatorPkg (I use Visual Studio 2017 ). First is in GenPcdDb.py, this error means parameter used to unpack is zero, please refer below :
Second is in tools_def.txt, this error means there is missing slash before nasm.exe, please refer below :
You can search “clouddai-test” in Attachment so that you will easy understand what I say. If I need submit more official document for become a contributor please let me know, or if my modification need obey some rule please also let me know, I am waiting your response
[-- Attachment #2: Type: text/html, Size: 4427 bytes --]
next reply other threads:[~2019-06-30 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 23:05 Hiber He [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-30 23:13 [edk2-devel] May I become a contributor in EmulatorPkg ? Hiber He
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=759a7bea.127.16baaa2d136.Coremail.hiberhe@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