You've already forked slimbootloader
mirror of
https://github.com/Dasharo/slimbootloader.git
synced 2026-03-06 15:26:20 -08:00
416f2d95da
* Sync BaseTools to align with edk2-stable202311 Keep the SBL specific change (e.g. Lz4). Signed-off-by: Guo Dong <guo.dong@intel.com> * feat: Sync MdePkg from EDK2 edk2-stable202311 branch Only sync required file without any changes to EDK2 files. Signed-off-by: Guo Dong <guo.dong@intel.com> * feat: Update MdePkg for SBL after sync from EDK2 Signed-off-by: Guo Dong <guo.dong@intel.com> * Update SBL after updating Basetool and MdePkg After Sync BaseTool and MdePkg to edk2-stable202311, Need update SBL code to align with this change. Signed-off-by: Guo Dong <guo.dong@intel.com> * feat: rollback some changes after mdepkg sync New change from MdePkg requires new NASM version. To make sure NASM 2.14.02 still works, just rollback few changes. Signed-off-by: Guo Dong <guo.dong@intel.com> * feat: Update component size to fix build failure After syncing BaseTool and MdePkg, some components would have a little bigger size. So update the config to fix the build failure. Signed-off-by: Guo Dong <guo.dong@intel.com> * feat: Remove unused asl code Some ASL files don't exist but they are included in other asl files. It would cause build failure with new build BaseTool. So just remove them to fix the build failure. Signed-off-by: Guo Dong <guo.dong@intel.com> --------- Signed-off-by: Guo Dong <guo.dong@intel.com>
49 lines
1.7 KiB
ReStructuredText
49 lines
1.7 KiB
ReStructuredText
::
|
|
|
|
Note: New build instructions are available. It is recommended to start with
|
|
the new instructions if learning how to build edk2 and/or BaseTools for the
|
|
first time. This page is retained for reference.
|
|
|
|
New instructions: `Build Instructions`_
|
|
|
|
.. _`Build Instructions`: https://github.com/tianocore/tianocore.github.io/wiki/Build-Instructions
|
|
|
|
This directory contains the EDK II build tools and template files.
|
|
Templates are located in the Conf directory, while the tools executables for
|
|
Microsoft Windows Operating Systems are located in the Bin\\Win32 directory, other
|
|
directory contains tools source.
|
|
|
|
Build step to generate the binary tools
|
|
---------------------------------------
|
|
|
|
Windows/Visual Studio Notes
|
|
===========================
|
|
|
|
To build the BaseTools, you should run the standard vsvars32.bat script
|
|
from your preferred Visual Studio installation or you can run get_vsvars.bat
|
|
to use latest automatically detected version.
|
|
|
|
In addition to this, you should set the following environment variables::
|
|
|
|
* EDK_TOOLS_PATH - Path to the BaseTools sub directory under the edk2 tree
|
|
* BASE_TOOLS_PATH - The directory where the BaseTools source is located.
|
|
(It is the same directory where this README.rst is located.)
|
|
|
|
After this, you can run the toolsetup.bat file, which is in the same
|
|
directory as this file. It should setup the remainder of the environment,
|
|
and build the tools if necessary.
|
|
|
|
Unix-like operating systems
|
|
===========================
|
|
|
|
To build on Unix-like operating systems, you only need to type ``make`` in
|
|
the base directory of the project.
|
|
|
|
Ubuntu Notes
|
|
============
|
|
|
|
On Ubuntu, the following command should install all the necessary build
|
|
packages to build all the C BaseTools::
|
|
|
|
sudo apt install build-essential uuid-dev
|