So the error message would be more accurate as:
only these system environment variables are permitted in the path
of an included file: $(WORKSPACE), $(ECP_SOURCE), $(EFI_SOURCE),
$(EDK_SOURCE)
From: Liu, Yingke D [mailto:[email protected]]
Sent: Monday, December 15, 2014 11:49 PM
To: [email protected]
Subject: Re: [edk2] build.exe !include Processing is Broken
Jim,
FDF spec limited that only $(WORKSPACE), $(ECP_SOURCE), $(EFI_SOURCE),
$(EDK_SOURCE) can be contained in !include path.
Dennis
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]]
Sent: Thursday, December 11, 2014 11:57 PM
To: [email protected]<mailto:[email protected]>
Subject: [edk2] FW: build.exe !include Processing is Broken
It seems build.exe cannot handle 2 DEFINE references in a "!include" statement,
and
it emits a misleading error message to boot:
Processing meta-data .
build...
u:\<somePkg>\<somePkg>.fdf(70):
error 3000: Invalid syntax/format
only these system environment variables are permitted to start the path
of the included file: $(WORKSPACE), $(ECP_SOURCE), $(EFI_SOURCE),
$(EDK_SOURCE)
near line 70, column 12:
$(WORKSPACE)/$(<somePathVar>)/PlatformConfig.dsc
- Failed -
Here is the entirety of line 70:
000000000111
123456789012
!include $(WORKSPACE)/$(<somePathVar>)/PlatformConfig.dsc
Perhaps someone who is able to create build.exe from the Python source could
fix this???
Thanks,
Jim
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
