public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Aleksey Shevandin <alexey@kazuar-tech.com>
To: edk2-devel@lists.01.org
Subject: TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)?
Date: Sun, 15 Apr 2018 18:23:06 +0300	[thread overview]
Message-ID: <d9059c6b-014d-cc7f-34ea-4453154e4b7a@kazuar-tech.com> (raw)

Dear members,

I'm trying to build *UDK2018* on *Ubuntu 17*. After studying the 
documentation, I had impressed that the platform setup script 
(*sedksetup.sh*) shall configure the build framework to target the 
correct build platform, the tool chain etc. Unfortunately this is not 
what actually happens.

The platform build process (the Build base tool) unexpectedly tries to 
build some *MS Windows* oriented stuff and fails. How this can be fixed?

Following the documented recommendations, at the first stage I build the 
"Base Tools":

|/make all -C ${EDK_TOOLS_PATH}/|

Then I run the setup script:

|/edksetup.sh BaseTools/|

This stages are finished with success, also the setup script runs some 
tests that successfully pass.

On the next stage I'm trying to build the platform:

|build all -a X64 -t GCC5|

This last stage fails with the follow error:

Nt32Pkg/Include/WinNtPeim.h:27:10: fatal error: Common/WinNtInclude.h: 
No such file or directory


Regards,

Aleksey



             reply	other threads:[~2018-04-15 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15 15:23 Aleksey Shevandin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-15 15:31 TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)? Marvin Häuser
2018-04-16 15:32 ` Richardson, Brian

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=d9059c6b-014d-cc7f-34ea-4453154e4b7a@kazuar-tech.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