Hi Folks,
In order for the nightly build to automatically pickup any binary or supporting
file in the BaseTools\Bin\Win32 directory, I would like to propose that we add
the attached file in the BaseTools\Source directory.
This allows a developer to add a new tool in either the C or Python 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.
Please provide feedback by Friday, Sep. 5th, 2014.
Thanks,
Larry
Larry Hauch
Intel Corporation
SSG, STO, Platform Software Infrastructure
2800 Center Dr.
DuPont, WA 98327
Work: (253) 371-8550
## @file
# This file lists all of the tool files that must be present in the Bin trees.
#
# This file is used by the EDK II Build Server that automatically builds the
# BaseTools Win32 binaries.
# When new tools are create, the tool executable must be listed in the
[Bin.Win32]
# section.
# If a tool requires additional files, the developer must list those files in
the
# [ExtraFiles.Win32] section.
# The [CxFreeze.Win32] section is maintained by the owner of the Build Server
who
# must ensure that files that are required by the cx_freeze frozen binaries are
# present in the Bin\Win32 directory.
#
# Copyright (c) 2014, Intel Corporation. All rights reserved.<BR>
#
# This program and the accompanying materials are licensed and made available
under
# the terms and conditions of the BSD License which accompanies this
distribution.
# The full text of the license may be found at:
# http://opensource.org/licenses/bsd-license.php
#
# THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,
# WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
#
##
[Bin.Win32]
build.exe
BPDG.exe
BootSectImage.exe
Common.PyUtility.pyd
EfiCompressor.pyd
EfiLdrImage.exe
EfiRom.exe
Eot.EfiCompressor.pyd
Eot.LzmaCompressor.pyd
GenBootSector.exe
GenCrc32.exe
GenDepex.exe
GenFds.exe
GenFfs.exe
GenFv.exe
GenFw.exe
GenPage.exe
GenPatchPcdTable.exe
GenSec.exe
GenVtf.exe
ImportTool.bat
LzmaCompress.exe
LzmaF86Compress.bat
PatchPcdValue.exe
Rsa2048Sha256GenerateKeys.exe
Rsa2048Sha256Sign.exe
Split.exe
TargetTool.exe
TianoCompress.exe
Trim.exe
UPT.exe
VfrCompile.exe
VolInfo.exe
[ExtraFiles.Win32]
TestSigningPrivateKey.pem
msvcr71.dll
[CxFreeze.Win32]
_ctypes.pyd
_hashlib.pyd
_socket.pyd
_sqlite3.pyd
_ssl.pyd
pyexpat.pyd
python27.dll
select.pyd
sqlite3.dll
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
