| Host Type & Toolchain | Build Status | Test Status | Code Coverage |
|---|---|---|---|
| Windows_VS |  |
 |
|
| Ubuntu_GCC5 |  |
|
This repository is part of Project Mu. Please see Project Mu for details https://microsoft.github.io/mu
This Configuration feature repo contains the generic Config Editor tools from Intel's Slim Bootloader repo which has been refactored to support more general use and with added functionality.
Far more details about using this repo can be found in: Configuration Applications Design.
Like other Project MU feature repositories, the Project MU Configuration feature repo does not strictly follow the EDKII releases, but instead has a continuous main branch which will periodically receive cherry-picks of needed changes from EDKII. For stable builds, release tags will be used instead to determine commit hashes at stable points in development. Release branches may be created as needed to facilitate a specific release with needed features, but this should be avoided.
Since this project does not follow the release fork model, the code should be consumed from a release hash and should be consumed as a extdep in the platform repo. To include, create a file named feature_config_ext_dep.yaml desired release tag hash. This could be in the root of the project or in a subdirectory as desired.
- {
"scope": "global",
"type": "git",
"name": "FEATURE_CONFIG",
"var_name": "FEATURE_CONFIG_PATH",
"source": "https://github.com/microsoft/mu_feature_config.git",
"version": "<RELEASE HASH>",
"flags": ["set_build_var"]
}
Setting the the var_name and the set_build_var flags will allow the build scripts to reference the extdep location. To make sure that the package is discoverable for the build, the following line should also be added to the build configurations GetPackagesPath list.
shell_environment.GetBuildVars().GetValue("FEATURE_CONFIG_PATH", "")
Note: If using pytool extensions older then version 0.17.0 you will need to append the root path to the build variable string.
After this the package should be discoverable to can be used in the build like any other dependency.
The SetupDataPkg/Tools folder contains Utilities that can enable working with Setup data
| Utility | Usage |
|---|---|
| SetupDataPkg/Tools/ConfigEditor.py | Configuration utility for creating/modifying SVD,XML configurations |
| SetupDataPkg/Tools/GenCfgData.py | Utility to generate output configuration structres from input YAML configurations |
| SetupDataPkg/Tools/VariableList.py | Utility to generate EFI dmpstore foramtted binaries, or csv file based on XML configuration |
| SetupDataPkg/Tools/WrapAndSetSvd.py | Utility to generate Dfci formatted output from input SVD file. |
This project has adopted the Microsoft Open Source Code of Conduct https://opensource.microsoft.com/codeofconduct/
For more information see the Code of Conduct FAQ https://opensource.microsoft.com/codeofconduct/faq/ or contact opencode@microsoft.com. with any additional questions or comments.
Contributions are always welcome and encouraged! Please open any issues in the Project Mu GitHub tracker and read https://microsoft.github.io/mu/How/contributing/
- [Code Requirements](https://microsoft.github.io/mu/CodeDevelopment/requirements/)
- [Doc Requirements](https://microsoft.github.io/mu/DeveloperDocs/requirements/)
Please open any issues in the Project Mu GitHub tracker. [More Details](https://microsoft.github.io/mu/How/contributing/)
Please follow the steps in the Project Mu docs to build for CI and local testing. [More Details](https://microsoft.github.io/mu/CodeDevelopment/compile/)
SPDX-License-Identifier: BSD-2-Clause-Patent
Upstream License (Slim Bootloader) ===================
Copyright (c) 2019, Intel Corporation and contributors. All rights reserved.
SPDX-License-Identifier: BSD-2-Clause-Patent
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Subject to the terms and conditions of this license, each copyright holder and contributor hereby grants to those receiving rights under this license a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except for failure to satisfy the conditions of this license) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer this software, where such license applies only to those patent claims, already acquired or hereafter acquired, licensable by such copyright holder or contributor that are necessarily infringed by:
- their Contribution(s) (the licensed copyrights of copyright holders and non-copyrightable additions of contributors, in source or binary form) alone; or
- combination of their Contribution(s) with the work of authorship to which such Contribution(s) was added by such copyright holder or contributor, if, at the time the Contribution is added, such addition causes such combination to be necessarily infringed. The patent license shall not apply to any other combinations which include the Contribution.
Except as expressly stated above, no rights or licenses from any copyright holder or contributor is granted under this license, whether expressly, by implication, estoppel or otherwise.
DISCLAIMER
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.