public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Pete Batard <pete@akeo.ie>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 1/1] MdeModulePkg/EbcDxe: add EBC Debugger configuration application
Date: Thu, 24 Nov 2016 13:06:23 +0000	[thread overview]
Message-ID: <81f1910c-8ed9-bd76-1363-962bd82dca4b@akeo.ie> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50386DA4D5@shsmsx102.ccr.corp.intel.com>

Hi Jiewen,

Thanks for clarifying the dependency restrictions. This is something I 
had been wondering about when I ported the app.

I'll work on removing the unwanted libraries and submit a v2.

Regards,

/Pete

On 2016.11.24 12:40, Yao, Jiewen wrote:
> Thank you Peter. I like this porting work.
>
> One comment is that we have special restriction on package dependency.
>  -- The MdeModulePkg should not depend upon ShellPkg.
>  -- The MdeModulePkg can only depend upon MdePkg.
>
> I know you want to parse the shell argument, such as Argc and Argv.
> If an application has ShellPkg dependency issue, the recommended way is to use EFI_SHELL_PARAMETERS_PROTOCOL, which is defined in UEFI SHELL 2.x specification.
>  -- It is located in MdePkg\Include\Protocol\ShellParameters.h
>
> An application may use ShellLib, if and only if it can depend upon ShellPkg, such as a platform Package, or ShellPkg itself.
>
> You can refer to MdeModulePkg\Application\CapsuleApp\AppSupport.c, GetArg() to see how to get Argv and Argc via EFI_SHELL_PARAMETERS_PROTOCOL. :-)
>
> Other part looks good to me.
>
> Thank you
> Yao Jiewen



      reply	other threads:[~2016-11-24 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 11:29 [PATCH 0/1] MdeModulePkg/EbcDxe: add EBC Debugger configuration application Pete Batard
2016-11-24 11:29 ` [PATCH 1/1] " Pete Batard
2016-11-24 12:40   ` Yao, Jiewen
2016-11-24 13:06     ` Pete Batard [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=81f1910c-8ed9-bd76-1363-962bd82dca4b@akeo.ie \
    --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