public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Wim Vervoorn <wvervoorn@eltan.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: UEFIPayload build issue
Date: Fri, 21 Sep 2018 07:37:09 +0000	[thread overview]
Message-ID: <4484ce34f4dd4b34a8b7edb06b07dc15@Eltsrv03.Eltan.local> (raw)
In-Reply-To: <B9726D6DCCFB8B4CA276A9169B02216D52112D1D@SHSMSX103.ccr.corp.intel.com>

Hello Zhu,

I am indeed using cxfreeze as is normally recommended. It will remove these binaries and use the tools from source.


Best Regards,
Wim Vervoorn




-----Original Message-----
From: Zhu, Yonghong [mailto:yonghong.zhu@intel.com] 
Sent: Friday, September 21, 2018 9:33 AM
To: Wim Vervoorn <wvervoorn@eltan.com>; edk2-devel@lists.01.org
Cc: Zhu, Yonghong <yonghong.zhu@intel.com>
Subject: RE: UEFIPayload build issue

Hi Wim Vervoorn,

May I know your steps? 
From the error message, seems you freeze the BaseTools to binary exe file,  and this failure was caused by the cxfreeze step.
We recommend run BaseTools Python from source in Windows. Thanks.

Best Regards,
Zhu Yonghong


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Wim Vervoorn
Sent: Friday, September 21, 2018 4:44 AM
To: edk2-devel@lists.01.org
Subject: [edk2] UEFIPayload build issue



Hello,

I am trying to build the new UEFIPayload from the staging repo.

The build proceeds pretty well but then I got this message:

Traceback (most recent call last):
  File "C:\Python27\lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
    exec(code, m.__dict__)
  File "GenFds\GenFds.py", line 24, in <module>
ValueError: Attempted relative import in non-package


build.exe...
: error 7000: Failed to execute command
        GenFds -f C:\git\SlimBootPayload\UEFIPayload\UefiPayloadPkg\UefiPayloadPkg.fdf --conf=c:\git\slimbootpayload\edk2\conf -o c:\git\slimbootpayload\edk2\Build\UefiPayloadPkgX64\DEBUG_VS2015x86 -t VS2015x86 -b DEBUG -p C:\git\SlimBootPayload\UEFIPayload\UefiPayloadPkg\UefiPayloadPkgIA32X64.dsc -a IA32,X64  -D "EFI_SOURCE=c:\\git\\slimbootpayload\\edk2\\edkcompatibilitypkg"  -D "EDK_SOURCE=c:\\git\\slimbootpayload\\edk2\\edkcompatibilitypkg"  -D "TOOL_CHAIN_TAG=VS2015x86"  -D "TOOLCHAIN=VS2015x86"  -D "TARGET=DEBUG"  -D "FAMILY=MSFT"  -D "WORKSPACE=c:\\git\\slimbootpayload\\edk2"  -D "EDK_TOOLS_PATH=c:\\git\\slimbootpayload\\edk2\\basetools"  -D "BD_ARCH=IA32X64"  -D "ARCH=IA32 X64"  -D "ECP_SOURCE=c:\\git\\slimbootpayload\\edk2\\edkcompatibilitypkg" [C:\git\SlimBootPayload\edk2]

- Failed -

So far I haven’t figured out what is causing this issue. It is good to note that use the tools from the master of the edk2 repo (status of today).

Suggestions are welcome.

Wim Vervoorn

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

      reply	other threads:[~2018-09-21  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 20:44 UEFIPayload build issue Wim Vervoorn
2018-09-21  7:32 ` Zhu, Yonghong
2018-09-21  7:37   ` Wim Vervoorn [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=4484ce34f4dd4b34a8b7edb06b07dc15@Eltsrv03.Eltan.local \
    --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