summaryrefslogtreecommitdiffstats
path: root/BaseTools/Source/BinaryFiles.txt
Commit message (Collapse)AuthorAgeFilesLines
* BaseTools: Add DevicePath support for PCD valuesYonghong Zhu2017-12-311-1/+2
| | | | | | | | | | | | Use C code parse device path to output hex string, and Python run command when PCD Value need device path parse. https://bugzilla.tianocore.org/show_bug.cgi?id=541 Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Yunhua Feng <yunhuax.feng@intel.com> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com> Reviewed-by: Liming Gao <liming.gao@intel.com>
* BaseTools: update BinaryFiles.txt file to add Pkcs7Sign ToolYonghong Zhu2016-08-231-1/+8
| | | | | | | | | | | add Pkcs7Sign.exe and related pem file into BinaryFiles.txt for build server to automatically build the binary win32 files. Cc: Liming Gao <liming.gao@intel.com> CC: Erik Bjorge <erik.c.bjorge@intel.com> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com> Reviewed-by: Erik Bjorge <erik.c.bjorge@intel.com>
* Removing the msvcr71.dll - no longer required, building with VS2013.lhauch2015-06-091-1/+0
| | | | | | | | Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: lhauch <larry.hauch@intel.com> Reviewed-by: Joe Peterson <joe.peterson@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17602 6f19259b-4bc3-4df7-8a09-765794883524
* Updated for ECC.exelhauch2015-04-101-0/+3
| | | | | | | | Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: lhauch <larry.hauch@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17163 6f19259b-4bc3-4df7-8a09-765794883524
* This file allows a developer to add a new tool in either the C or Python ↵lhauch2014-09-051-0/+74
trees, add the executable (and any supporting files, such as the TestSigningPrivateKey.pem file) to this file and the build server will automatically make sure that the new files are added to the BaseTools\Bin\Win32 directory. The Win32 directory is located in https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32 repository. Developer - Tool add process: 1) Developer adds code for the new tool. 2) Developer updates the Makefile in the C or Python directory a) The entry must make sure that the executable is generated in the BaseTools\Bin\Win32 directory and any supporting files are copied to the same directory as part of the build step. 3) Developer adds the <Toolname>.exe under the [Bin.Win32] section in the BinaryFiles.txt file. 4) Developer adds other files required to be present in the [ExtraFiles.Win32] section in the BinaryFiles.txt file. Build Server: 1) Build all binaries by calling nmake on the Source\C\Makefile and Source\Python\Makefile 2) After building the binaries, the build server verify that the files listed in BaseTools\Source\BinFiles.txt are also in the edk2-toolbinaries project, a. If a file is not under source control, then the build server will add file as long as it is present. File format: [SectionName.TargetDir] File1 File2 … Where: SectionName is one of Bin, ExtraFiles or CxFreeze TargeDir is the name of the subdirectory in the BaseTools\Bin directory tree. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: lhauch <larry.hauch@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@16063 6f19259b-4bc3-4df7-8a09-765794883524