public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Richardson, Brian" <brian.richardson@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)?
Date: Mon, 16 Apr 2018 15:32:46 +0000	[thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AFA47BB757@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <VI1PR0801MB17904D165338519862BC2DAF80B10@VI1PR0801MB1790.eurprd08.prod.outlook.com>

I recommend you try building MdePkg as a test under any Linux environment. NT32Pkg is designed for Windows environments.

https://github.com/tianocore/tianocore.github.io/wiki/UDK2018-How-to-Build#how-to-build-linux-like-system 

Thanks . br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software
brian.richardson@intel.com -- @intel_brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson 


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Marvin Häuser
Sent: Sunday, April 15, 2018 11:31 AM
To: edk2-devel@lists.01.org
Subject: Re: [edk2] TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)?

Hey,

As you have found out, Nt32Pkg is for Windows and shouldn't be built on Linux.
You can specify the platform descriptor file to build via the "-p <PathToDsc>" parameter.

Regards,
Marvin.

> -----Ursprüngliche Nachricht-----
> Von: edk2-devel <edk2-devel-bounces@lists.01.org> Im Auftrag von 
> Aleksey Shevandin
> Gesendet: Sonntag, 15. April 2018 17:23
> An: edk2-devel@lists.01.org
> Betreff: [edk2] TianoCore UEFI Development Kit build: how to cause the 
> build process to correctly recognize the build platform (Linux)?
> 
> 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
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-15 15:23 Aleksey Shevandin

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=80AC2BAA3152784F98F581129E5CF5AFA47BB757@ORSMSX114.amr.corp.intel.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