public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
* Re: TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)?
@ 2018-04-15 15:31 Marvin Häuser
  2018-04-16 15:32 ` Richardson, Brian
  0 siblings, 1 reply; 3+ messages in thread
From: Marvin Häuser @ 2018-04-15 15:31 UTC (permalink / raw)
  To: edk2-devel@lists.01.org

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


^ permalink raw reply	[flat|nested] 3+ messages in thread
* TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)?
@ 2018-04-15 15:23 Aleksey Shevandin
  0 siblings, 0 replies; 3+ messages in thread
From: Aleksey Shevandin @ 2018-04-15 15:23 UTC (permalink / raw)
  To: edk2-devel

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-04-16 15:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
  -- strict thread matches above, loose matches on Subject: below --
2018-04-15 15:23 Aleksey Shevandin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox