mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-10 01:16:06 +00:00
When I build a release acrn with a debug scenario like this: $ BOARD=nuc11tnbi5 SCENARIO=shared make -j1 RELEASE=y Following logs are repeated endlessly. /home/abc/workspace/mainline/acrn-hypervisor/build/hypervisor/configs/allocation.xml generated /home/abc/workspace/mainline/acrn-hypervisor/build/hypervisor/configs/unified.xml generated /home/abc/workspace/mainline/acrn-hypervisor/build/hypervisor/configs/config.mk generated scripts/makefile/config.mk:191: The command line sets RELEASE to be 'y', but an existing build is configured with 'n' scripts/makefile/config.mk:191: The configuration will be modified for RELEASE=y Because "BUILD_TYPE" was moved out of "DEBUG_OPTIONS" in scenario file, outdated transform script fails to extract information there and it always set 'CONFIG_RELEASE=n'. If a makefile is included with a rule for it, the rule will be executed first to generated new makefile. If it's updated, the make process will be reexecuted with new makefile. In the case above, build/hypervisor/configs/config.mk rule is executed every time make tries to include it. Unhandled different between `RELEASE` and `CONFIG_RELEASE` causes determine_build_type to update .scenario.xml which is a dependency of hypervisor/scripts/makefile/config.mk. Tracked-On: #7657 Signed-off-by: Qiang Zhang <qiang4.zhang@intel.com> |
||
---|---|---|
.. | ||
acpi_gen | ||
acpi_template/template | ||
board_config | ||
board_inspector | ||
configurator | ||
data | ||
hv_config | ||
launch_config | ||
library | ||
scenario_config | ||
schema | ||
service_vm_config | ||
static_allocators | ||
xforms | ||
build.cmd | ||
LICENSE | ||
MANIFEST.in | ||
pyproject.toml | ||
README.md | ||
setup.cfg |
Supporting libraries of ACRN configuration toolset
This package contains the libraries supporting ACRN configuration toolset, including:
- The manipulators and validators of scenario schemas or XMLs
- The generator of guest ACPI tables
The main objective of this package is to ease the import of the supporting libraries in the ACRN configurator which uses a Python interpreter built in WebAssembly (WASM). This package is thus NOT intended to be used by users; invoke the Python scripts directly if needed.