cannot generate AutoGen.* files. Only "build" command can.\r
3) build.exe in %WORKSPACE%\BaseTools\Bin\Win32 is generated from following revision of\r
Python source code:\r
- r729 <buildtools_project>\BaseTools\Source\Python\Autogen\r
- r729 <buildtools_project>\BaseTools\Source\Python\build\r
- r729 <buildtools_project>\BaseTools\Source\Python\Common\r
- r729 <buildtools_project>\BaseTools\Source\Python\CommonDataClass\r
- r729 <buildtools_project>\BaseTools\Source\Python\GenFds\r
+ r844 <buildtools_project>\BaseTools\Source\Python\Autogen\r
+ r844 <buildtools_project>\BaseTools\Source\Python\build\r
+ r844 <buildtools_project>\BaseTools\Source\Python\Common\r
+ r844 <buildtools_project>\BaseTools\Source\Python\CommonDataClass\r
+ r844 <buildtools_project>\BaseTools\Source\Python\GenFds\r
\r
4) GenFds.exe has is a combo of the follow python source.(This is a temporary branch)\r
- r729 <buildtools_project>\BaseTools\Source\Python\Common\r
- r729 <buildtools_project>\BaseTools\Source\Python\CommonDataClass\r
- r729 <buildtools_project>\BaseTools\Source\Python\GenFds\r
+ r843 <buildtools_project>\BaseTools\Source\Python\Common\r
+ r843 <buildtools_project>\BaseTools\Source\Python\CommonDataClass\r
+ r843 <buildtools_project>\BaseTools\Source\Python\GenFds\r
\r
Brief usage for Migration Tool MigrationMsa2Inf.exe:\r
1. Command line format:\r
PcdLib|MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf\r
}\r
\r
-30-August-2007\r
+Brief usage for Migration Tool Spd2Dec.exe:\r
+1. Command line format:\r
+ Spd2Dec [options] input_filename\r
+2. Input File:\r
+ A syntactically valid SPD file\r
+3. Output Files:\r
+ A DEC file whose syntax confirms to DEC spec.\r
+ \r
+4. Example:\r
+ a. Spd2Dec -o c:\work\EdkII\Nt32Pkg\Nt32.spd c:\work\EdkII\Nt32Pkg\Nt32.dec\r
+ b. Spd2Dec -a c:\work\EdkII\Nt32Pkg\Nt32.spd\r
+ Example a & b are equivalent to migrate Nt32 package SPD file from EDKII to EDKII' snytax.\r
+ \r
+6. Pyton Source\r
+ r777 <buildtools_project>\BaseTools\Source\Python\spd2Dec\r
+\r
+Brief usage for Migration Tool Fpd2Dsc.exe:\r
+1. Command line format:\r
+ Fpd2Dsc [options] input_filename\r
+2. Input File:\r
+ A syntactically valid FPD file\r
+3. Output Files:\r
+ A DSC file which syntax confirms to DSC spec.\r
+4. Prerequisite:\r
+ a. The workspace directory must be specified either by environment variable or -w option.\r
+ \r
+5. Example:\r
+ WORKSAPCE has already been set: $(WORKSPACE) = c:\work\EdkII. \r
+ \r
+ a. Fpd2Dsc -o c:\work\EdkII\Nt32Pkg\Nt32.dsc c:\work\EdkII\Nt32Pkg\Nt32.fpd\r
+ b. Fpd2Dsc -a c:\work\EdkII\Nt32Pkg\Nt32.fpd\r
+ Example a & b are equivalent to migrate Nt32 platform description file from EDKII to EDKII' snytax.\r
+ \r
+6. Known Limitations:\r
+ a. Tool does not handle Libraries Section since no related info in original FPD file. Developers need to handle it manually in the output DSC file.\r
+ b. If MSA file which is corresponds to module guid could not be found in currect workspace, tool will dump the module guid.\r
+ \r
+7. Pyton Source\r
+ r767 <buildtools_project>\BaseTools\Source\Python\Fpd2Dsc\r
+\r
+27-September-2007\r