Eugene: The formal way is to add this support in [FD] section. The workaround way is to create two FDF files, one is for inner FD, another is for out FD. Out FDF will use FILE statement to point to the generated inner FD image. Then, call build -p platform.dsc twice. First, call build -p platform.dsc -f inner.fdf, Last, call build -p platform.dsc -f out.fdf.
Thanks Liming -----Original Message----- From: edk2-devel [mailto:[email protected]] On Behalf Of Cohen, Eugene Sent: Wednesday, December 23, 2015 10:42 PM To: [email protected]; Zhu, Yonghong Subject: [edk2] Nested FD files in one FDF We have a need to have one FD image embedded in another (two copies of an identical FD image). So in our platform FDF file we'd like to define one FD for the "outer" region and another FD for the "inner" region. We then would like to specify in the outer FD a file that is the inner FD. Something like: [FD.Outer] <header sutff> 0x00000000|0x00100000 FILE = INNER.fd [FD.Inner] <the usual FV stuff> For this to work the build either needs to understand the dependency or at least have deterministic ordering for evaluating FDs so we can ensure that the inner one is created before the outer one. If this approach doesn't work, are there other recommendations for how to nest FDs? I've found that invoking build twice is expensive since the second invocation may try to do builds when we only want the Outer FDF to be processed. I was hoping to find a way to solve this under the existing build specs and BaseTools implementation but if this isn't possible then we could discuss extending the FDF syntax to allow a new "FD = <FdUiName>" region within the [FD] section to specify explicit FD nesting. Thanks for the help, Eugene _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
