Hi Tim,

In general, we have tried to limit what is in the formal EDK II DEC/INF 
sections to items that are required to build.  Information not required to 
build goes into comments or UserDefined sections.  Given that this proposed 
user defined section lists a set of files with module/package relative paths 
with the same format as a INF [Sources] or [Binaries] section, we preferred 
using a TianoCore user extension to list those files instead of using comments. 
 These files can include the UNI file I described below or readme files, other 
documentation files, or any file that is associated with the module/package, 
but not required to build.

UNI file syntax is not being changed.  Some specific string token names are 
being proposed for the ABSTRACT/DESCRPTION so the UPT tool can convert them to 
current packaging specification defined format for that content.

The UDP Spec and UPT tool already have the required behavior that user defined 
sections are passed through "as is", so no packaging specification changes are 
required for sections of that type.  In some cases there is an advantage to 
using a user defined section for some types of information content because it 
does not require a change to the packaging specification or the XML schema if 
only the pass through behavior is required.

Thanks,

Mike

From: Tim Lewis [mailto:tim.le...@insyde.com]
Sent: Wednesday, August 06, 2014 3:13 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] INF/DEC file updates to EDK II packages

Mike --

I am also curious why this EDK2 behavior is being put into a "UserDefined" 
section at all, since the file format is owned by the specifications on this 
web site.  why not just create a new [PackageInfo] section and update the 
revision level?

Are the contents of the new .UNI files and their tags also in a specification 
somewhere? Is there a description as to where this corresponds with items in 
the packaging specification?

Thanks,

Tim
________________________________
From: Kinney, Michael D [michael.d.kin...@intel.com]
Sent: Wednesday, August 06, 2014 2:31 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] INF/DEC file updates to EDK II packages
Hello,

I wanted to let everyone know about a number of patch reviews for EDK II 
packages that will be sent out over the next couple of weeks.  These patches 
impact the order of content in INF/DEC files and comment blocks in INF/DEC 
files, and should not have any build or functionality impacts.  These patches 
will address the following issues:


1)      Usage information in INF file comment blocks are either incomplete or 
incorrect.  This includes usage information for 
Protocols/PPIs/GUIDs/PCDs/HOBs/Events/BootModes.  The syntax for usage 
information in comment blocks is defined in the EDK II Module Information (INF) 
Specification

2)      Add MODULE_UNI_FILE to INF [Defines] section along with UNI file that 
contains the localized Abstract and Description of a module.

a.      Addresses an information gap between INF files and the UEFI 
Distribution Packaging Specification XML schema

b.      There will be an associated update to UPT in BaseTools to consume 
MODULE_UNI_FILE and associated UNI file during UDP creation that performs the 
INF -> XML conversion.

c.      There will be an associated update to UPT in BaseTools to produce 
MODULE_UNI_FILE and associated UNI file during UDP installation that performs 
the XML -> INF conversion.

3)      Add [UserExtensions.TianoCore."ExtraFiles"] section to INF files along 
with associated UNI file that provides the localized Name of a module.

a.      [UserExtensions.TianoCore."ExtraFiles"] provides an easy method for a 
module to specify extra files not listed in [Sources] or [Binaries] sections to 
be added to a UDP without having to list the files in the UPT package 
information data file.

b.      There will be an associated update to UPT in BaseTools to package up 
files listed in [UserExtensions.TianoCore."ExtraFiles"] during UDP creation.

c.      UNI file contains localized name of a module to go along with the 
localized Abstract and Description from the MODULE_UNI_FILE.

4)      PCD information in DEC file comment blocks are either incomplete or 
incorrect.  This includes detailed description, @Prompt, @ValidRange, 
@ValidList, @Expression, and [Error.<TokenSpaceGuid>] validation error messages

5)      Add PACKAGE_UNI_FILE to DEC [Defines] section along with UNI file that 
contains the localized Abstract and Description of a package and localized 
strings associated with PCDs.

a.      Addresses an information gap between DEC files and the UEFI 
Distribution Packaging Specification XML schema

b.      There will be an associated update to UPT in BaseTools to consume 
PACKAGE_UNI_FILE and associated UNI file during UDP creation that performs the 
DEC -> XML conversion.

c.      There will be an associated update to UPT in BaseTools to produce 
PACKAGE_UNI_FILE and associated UNI file during UDP installation that performs 
the XML -> DEC conversion.

6)      Add [UserExtensions.TianoCore."ExtraFiles"] section to DEC files along 
with associated UNI file that provides the localized Name of a package.

a.      [UserExtensions.TianoCore."ExtraFiles"] provides an easy method for a 
package to specify extra files to be added to a UDP without having to list the 
files in the UPT package information data file.

b.      There will be an associated update to UPT in BaseTools to package up 
files listed in [UserExtensions.TianoCore."ExtraFiles"] during UDP creation.

c.      UNI file contains localized name of a package to go along with the 
localized Abstract and Description from the PACKAGE_UNI_FILE.

7)      Make sure order of DEC/INF content matches the order that UPT generates 
in the XML -> INF conversion

a.      This allows UDP packages installed by UPT to be compared against EDK II 
trunk/branches using standard diff utilities.

Patches for the following EDK II packages are being prepared

1)      MdePkg

2)      MdeModulePkg

3)      IntelFrameworkPkg

4)      IntelFrameworkModulePkg

5)      FatPkg

6)      ShellPkg

7)      PcAtChipsetPkg

8)      UefiCpuPkg

9)      SourceLevelDebugPkg

10)   CryptoPkg

11)   SecurityPkg

12)   NetworkPkg

Best regards,

Mike

------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to