public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: 戴,曉政 <cloud0907@yahoo.com.tw>
To: "Feng, Bob C" <bob.c.feng@intel.com>, "Ni, Ray" <ray.ni@intel.com>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
	 "afish@apple.com" <afish@apple.com>,
	 "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: 回覆: May I become a contributor in EmulatorPkg ?
Date: Tue, 2 Jul 2019 00:14:56 +0800	[thread overview]
Message-ID: <MADEUP.15AD54A4265526CB.18305@groups.io> (raw)
In-Reply-To: <08650203BA1BD64D8AD9B6D5D74A85D160B386D3@SHSMSX105.ccr.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2028 bytes --]

Dear Bob,

Thanks for your reply. I already fix second issue. For first one, because I can’t execute edksetup.bat directly so I modify a little content of edksetup.bat, please see attachment and search “clouddai-test”. In addition, because there is no win32 bin file in I original edk2-master.zip, so I download it from Github, maybe this is key point. Waiting for your response.

寄件者: Feng, Bob C
傳送時間: 2019年7月1日 下午 06:10
收件者: Ni, Ray; ?,??
副本: Justen, Jordan L; afish@apple.com; devel@edk2.groups.io
主旨: RE: May I become a contributor in EmulatorPkg ? 

For the second issue, you have to set the NASM_PREFIX to a path which ends with a slash.

For the first one, could you provide the steps to reproduce it? 

Thanks,
Bob 

From: Ni, Ray 
Sent: Sunday, June 30, 2019 9:23 PM
To: Feng, Bob C <bob.c.feng@intel.com>
Cc: 戴,曉政 <cloud0907@yahoo.com.tw>; Justen, Jordan L <jordan.l.justen@intel.com>; afish@apple.com; devel@edk2.groups.io
Subject: RE: May I become a contributor in EmulatorPkg ? 

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 #1.2: Type: text/html, Size: 8959 bytes --]

[-- Attachment #2: edksetup.zip --]
[-- Type: application/zip, Size: 1957 bytes --]

[-- Attachment #3: image001.jpg --]
[-- Type: image/jpeg, Size: 53623 bytes --]

[-- Attachment #4: image002.jpg --]
[-- Type: image/jpeg, Size: 18478 bytes --]

  reply	other threads:[~2019-07-01 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ea573f1d-4a05-4775-ae43-3e265a760f72@orsmsx102.amr.corp.intel.com>
2019-06-30 13:22 ` May I become a contributor in EmulatorPkg ? Ni, Ray
2019-07-01 10:10   ` Bob Feng
2019-07-01 16:14     ` 戴,曉政 [this message]
2019-07-02 12:48     ` 回覆: " 戴,曉政
     [not found]     ` <ffaa1db5-47cc-4dbc-8886-8e240c8446e3@orsmsx104.amr.corp.intel.com>
2019-07-03  2:10       ` Bob Feng

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=MADEUP.15AD54A4265526CB.18305@groups.io \
    --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