mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-05-09 17:07:00 +00:00
03a9c78e8d
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> |
||
|---|---|---|
| .. | ||
| board_info.h.xsl | ||
| config_common.xsl | ||
| config.h.xsl | ||
| config.mk.xsl | ||
| ivshmem_cfg.h.xsl | ||
| lib.xsl | ||
| misc_cfg.h.xsl | ||
| pci_dev.c.xsl | ||
| pt_intx.c.xsl | ||
| vm_configurations.c.xsl | ||
| vm_configurations.h.xsl | ||