public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Hristo Mihaylov <hristo.mihaylov@prodrive-technologies.com>
Cc: edk2-devel@lists.01.org
Subject: Re: error C0DE: Unknown fatal error when processing
Date: Tue, 13 Feb 2018 19:37:22 +0100	[thread overview]
Message-ID: <dc3ab969-ba0a-8193-06fe-263b550bd8ff@redhat.com> (raw)
In-Reply-To: <3773dc75-6d95-d1f3-ee52-b9e440682fd3@prodrive-technologies.com>

Hi Hristo,

On 02/13/18 16:44, Hristo Mihaylov wrote:
> Hello,
> 
> I just hit this and it told me to send you the stack trace. I think it's
> due to the fact that I created an empty FDF file.
> 
> ```
> hrimih@lnxclnt2002:~/work/edk2.git$ build clean && build && cp
> Build/Hvmf/DEBUG_GCC5/X64/HelloWorld.efi ~/work/ovmf/hda-contents

[...]

> Active Platform          = /home/hrimih/work/edk2.git/HvmfPkg/HvmfPkg.dsc
> Flash Image Definition   = /home/hrimih/work/edk2.git/HvmfPkg/HvmfPkg.fdf

If you only want to build EFI binaries in your platform DSC file, then
you don't need an FDF file. Simply remove the FLASH_DEFINITION entry
from the [Defines] section of the DSC file.

edk2 contains several DSC files that only build EFI binaries, and no
flash images; for example:
- AppPkg/AppPkg.dsc
- ShellPkg/ShellPkg.dsc


If you want to build only one EFI file (regardless of whether you have a
FLASH_DEFINITION setting in your DSC file, or not), then you can pass the

  --module=Relative/Path/To/Module.inf

option to the "build" utility. Then "build" will only build "Module.inf".

Thanks
Laszlo


      reply	other threads:[~2018-02-13 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 15:44 error C0DE: Unknown fatal error when processing Hristo Mihaylov
2018-02-13 18:37 ` Laszlo Ersek [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=dc3ab969-ba0a-8193-06fe-263b550bd8ff@redhat.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