## Description
Checks if the rust-src component is installed for the workspace
toolchain.
This is a basic requirement to build firmware code and not having
rust-src can result in an obscure error during firmware build.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
- Verify with the `rust-src` component installed/uninstalled
- Check on Linux and Windows
## Integration Instructions
N/A - Instructions included in log output
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Этот файл содержит невидимые символы Юникода, которые могут быть отображены не так, как показано ниже. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы показать скрытые символы.
::
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
01abd5c3da