Thanks Mike. That leads me to the next point of confusion. Is the purpose
of the Platform Configuration Database (PCD) to share variables across
drivers, applications, and/or whatever is launching an app or driver; or is
it just a method the build system offers for you to define variables in a
configuration file instead of a .h header file?
On Thu, Jan 31, 2013 at 11:44 AM, Kinney, Michael D <
michael.d.kin...@intel.com> wrote:
> David,****
>
> ** **
>
> Yes. You can directly use libraries from a UEFI Application. There is an
> example Hello World UEFI Application in the MdeModulePkg that can be built
> for all supported CPU architectures and it also demonstrates use of
> libraries from the MdePkg and MdeModulePkg. The path is:
> MdeModulePkg\Application\HelloWorld\HelloWorld.inf****
>
> ** **
>
> To build just this one UEFI application for X64 from the command line
> using VS2008:****
>
> ** **
>
> **Ø **build -a X64 -t VS2008x86 -p MdeModulePkg\MdeModulePkg.dsc -m
> MdeModulePkg\Application\HelloWorld\HelloWorld.inf****
>
> ** **
>
> You can create your own package with your own UEFI applications following
> the HelloWorld example in the MdeModulePkg.****
>
> ** **
>
> The UEFI Driver Wizard found at the following link also provides easy ways
> to create new EDK II packages and add new UEFI drivers to a new package.
> You could use that tool to get started and then populate your own UEFI
> Applications into your own package.****
>
> ** **
>
>
> http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Driver_Developer
> ****
>
> ** **
>
> Best regards,****
>
> ** **
>
> Mike****
>
> ** **
>
> *From:* David F. [mailto:df7...@gmail.com]
> *Sent:* Thursday, January 31, 2013 11:20 AM
> *To:* edk2-devel@lists.sourceforge.net
> *Subject:* [edk2] help getting started creating efi x64 application using
> package system****
>
> ** **
>
> Hi,****
>
> So as a test I was able to create a x64 EFI application using VS2008
> command line by using some of the header files under mdepkg\include and
> mdepkg\include\X64 along with then genfw to convert the .dll to the .efi.
> This worked fine. But, I'm thinking it would be nice to use some of the
> existing libraries (especially to handle malloc/free, new/delete,
> open/close etc..) and not have to rebuild the wheel so to speak. The
> question is, would I need to figure out and use this "package" system with
> all its GUID's and defines, etc.. or can I just link to existing
> libraries? I wouldn't mind using the package system if it made since to
> me. Could someone indicate where/how you would add a general efi
> application, using the package system, that won't be in firmware or part of
> any package. It will be a stand alone app that can be run on any (x64 -
> Intel/AMD based) UEFI system.****
>
> Thanks!!
>
> ****
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
