Java Tools\r
Apache-ANT, version 1.6.5 or later (http://ant.apache.org)\r
Ant-contrib, version 1.0b2 or later\r
- (http://sourceforge.net/project/showfiles.php?group_id=36177)\r
+ (http://prdownloads.sourceforge.net/ant-contrib/ant-contrib-1.0b2-bin.zip?download)\r
Saxon8, version 8.1.1\r
(http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download)\r
- XMLBeans, version 2.1.0 or later (http://xmlbeans.apache.org) \r
+ XMLBeans, version 2.1.0 (http://xmlbeans.apache.org)\r
+ DO NOT download the latest XMLBeans, version 2.2.0. It cannot work with\r
+ Saxon8, version 8.1.1.\r
\r
Other Tools\r
TortoiseSVN version 1.3.3. (http://tortoisesvn.tigris.org/)\r
\r
The Java Environment Variable must be set before attempting to build.\r
i.e. For Sun JDK (see note below*):\r
- set JAVA_HOME=c:\ Java\jdk1.5.0_06 \r
+ set JAVA_HOME=c:\Java\jdk1.5.0_06 \r
i.e. For Bea Systems:\r
- set JAVA_HOME=c:\Program Files\Java\jrockit-R26.0.0-jdk1.5.0_04\r
+ set JAVA_HOME=c:\Java\jrockit-R26.0.0-jdk1.5.0_04\r
\r
*When using the Sun JDK5.0\r
During installation, you should specify the install directory as C:\Java\r
\r
The XMLBeans, requires the XMLBEANS_HOME environment variable to be set\r
before attempting to build:\r
- i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>\r
+ i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>\r
\r
The saxon8.jar file should be copied to the %XMLBEANS_HOME%\lib directory.\r
\r
The restictions are used to limit the build output by specifying build target(s), \r
tagname(s) and architecture(s) to less than the full set of possible options. \r
\r
-The ACTIVE_PLATFORM MUST BE SET. All other options need not be set, however by \r
-unsetting these options (by removing the line from the file, or leaving the Value \r
-empty) will result in all available build possibilites when typing build. By\r
-default EDK II can build a matrix of binaries, using different target types, tool\r
-chain tags and architectures. Options to target.txt file are as follows:\r
+The ACTIVE_PLATFORM must be set unless the current working directory contains one\r
+or more FPD files. All other options need not be set, however by unsetting these\r
+options (by removing the line from the file, or leaving the Value empty) will \r
+result in all available build possibilites when typing build. By default EDK II\r
+can build a matrix of binaries, using different target types, tool chain tags and \r
+architectures. Options to target.txt file are as follows:\r
\r
ACTIVE_PLATFORM = Value REQUIRED\r
Where Value is the WORKSPACE relative path and filename of a Framework Platform \r
element as described above.\r
\r
--------------------------------------- \r
-7) Define a new PCD entry in a package:\r
+7) Declare a new PCD entry in a package:\r
- This release requires manual editing of the SPD file to include the new\r
PCD. New Pcd entries are added to the PcdDefinitions section of the\r
<PackageName>.spd file using the following example for the format:\r
NOTE: The hex <Token> value must be unique.\r
\r
-<PcdDefinitions>\r
+<PcdDeclarations>\r
<PcdEntry ItemType="FIXED_AT_BUILD">\r
<C_Name>PcdMaximumUnicodeStringLength</C_Name>\r
<Token>0x00000001</Token>\r
+ <TokenSpaceGuidCName>gEfiMdePkgTokenSpaceGuid</TokenSpaceGuidCName>\r
<DatumType>UINT32</DatumType>\r
+ <ValidUsage>FIXED_AT_BUILD</ValidUsage>\r
<DefaultValue>1000000</DefaultValue>\r
+ <HelpText>The maximum lengh for unicode string.</HelpText>\r
</PcdEntry>\r
-</PcdDefinition>\r
+</PcdDeclarations>\r
\r
------------------------------\r
8) Declare a new Library Class:\r