As part of gaining familiarity with the ins and outs of the EDK II code base,
tools etc I added to EdkShellPkg the Shell directory as detailed in the
EdkShellPkg ReadMe.txt file and did a build using the .dsc of EdkShellPkg.
I see in the .dsc that both Shell.inf (minimum Shell) and ShellFull.inf are
called out to be built. On examination I realized they both build to the same
name to the same directory and as such only one exists after the build.
Looking deeper I see that back in 2009 a comment in the .dsc of" # #
Shell.inf & ShellFull.inf can not be included at once to avoid over #"was
removed but the comment is still valid.
Looking at EdkShellBinPkg the Shell files are name Shell.efi, for the minimum,
and Shell_Full.inf. The build detailed in the EdkShellBinPkg ReadMe.txt
explains how to perform the build and get both files. One thing it doesn't
explain in the readme is that the resulting file name for the ShellFull.inf
build seems to need to be renamed in each of the Arch directories to achieve
the naming of the checked out full binaries.
It seems adjusting the full shell's naming could streamline the process of
building files for EdkShellBinPkg. It seems like the alternative is that ReadMe
files for EdkShellBinPkg and EdkShellPkg could have detail added to discuss the
manual name change along with adding back a comment into EdkShellPkg.dsc to
warn of building Shell.inf and ShellFull.inf in the same build.
Is there something I've overlooked or misunderstood ?
Are the "Shell" and the EDK2 developers one in the same or is the coordination
between two developer groups limiting changes to resolve the name collision ?
I'm just trying to bring up a trap that others new to EDK2 may fall in, like I
have, that can frustrate and hinder them from going any further.
ThanksRichard
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
