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:[email protected]] On Behalf Of Wim
Vervoorn
Sent: Friday, September 21, 2018 4:44 AM
To: [email protected]
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
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
--- Begin Message ---
Hi, all
Now, we are working to migrate BaseTools Python tool from Python27 to
Python36. To reduce the migration effort, we will only verify BaseTools Python
tool run from source. That means we will stop to support the freeze python tool
as windows exe. In fact, we get the report that edk2-BaseTools-win32 doesn't
work. We don't plan to fix it. If you still use the freeze python tool exe,
please run BaseTools Python from source in Windows. Here is the step wiki
https://github.com/tianocore/tianocore.github.io/wiki/Windows-systems Compile
Tools section. After migrate to Python36, we will update wiki page to document
Python36 step.
>From now, we will stop to freeze python tool, remove
>Edk2\BaseTools\Source\Python\Makefile, and stop update edk2-BaseTools-win32
>github repo. And, I will reset edk2-BaseTools-win32 binary to match edk2
>vUDK2018 tag. If you require the freeze python tool, you can maintain your
>step to freeze the python tool. Here is the link
>https://docs.python-guide.org/shipping/freezing/ to introduce the different
>freezing solutions.
Thanks
Liming
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
--- End Message ---
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
