OrgACRN
/
acrn-hypervisor
mirror of https://github.com/projectacrn/acrn-hypervisor.git
1
0
Fork 0
Code Issues Releases Wiki Activity
acrn-hypervisor/Makefile

237 lines
8.7 KiB
Makefile
Raw Normal View History

Makefile: make hypervisor from specified Kconfig When user finish doing "make menuconfig", the .config file is saved in acrn-config/hypervisor/build/ by default. So current Makefile will check whether this customized .config file exists and then continue to do following make process. But this might not true in the real user case, user could put this customized .config file anywhere. To resolve this problem, the patch add a KCONFIG_FILE parameter to handle such case. When KCONFIG_FILE is specified, hypervisor could build hypervisor with the specific configuration file. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 22:40:14 +08:00
# acrn-hypervisor/Makefile
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
# global helper variables
T := $(CURDIR)
Makefile: separate PLATFORM into BOARD+FIRMWARE Combination of BOARD and FIRMWARE is a more precious definition. And we decide PLATFORM_XXX based on FIRMWARE, remove relative one in board config. We reserve PLATFORM for backward compatibility. Tracked-On: #1995 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Yin Fengwei < fengwei.yin@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2018-12-11 16:00:56 +08:00
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
TARGET_DIR ?=
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
# BOARD/SCENARIO/BOARD_FILE/SCENARIO_FILE/KCONFIG_FILE parameters sanity check:
#
# Only below usages are VALID: (target = all | hypervisor)
# 1. make <target>
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
# 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx]
# 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx]
# 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx]
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
#
# Especially for case 1 that no any parameters are specified:
# a. If hypervisor/build/.config file which generated by "make menuconfig" exist,
# the .config file will be loaded as KCONFIG_FILE:
# i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config
#
# b. If hypervisor/build/.config file does not exist,
# the default BOARD/SCENARIO will be loaded:
# i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO)
#
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
# For case 2/3, configurations are imported from TARGET_DIR when TARGET_DIR is specified;
Makefile: disable KCONFIG_FILE when build from xml The SCENARIO xml file already includes all information of KCONFIG file, use KCONFIG_FILE/SCENARIO_FILE parameter at same time would introduce conflict so this case should be invalid. Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-16 09:54:43 +08:00
# For case 4, configurations are from XML files and saved to TARGET_DIR if it is specified;
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
#
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
# The grep process did not handle corner case when '#' is manually put right after config value as comments,
# i.e. it will be failed in the case of "CONFIG_XXX=y # some comments here "
Makefile: make hypervisor from specified Kconfig When user finish doing "make menuconfig", the .config file is saved in acrn-config/hypervisor/build/ by default. So current Makefile will check whether this customized .config file exists and then continue to do following make process. But this might not true in the real user case, user could put this customized .config file anywhere. To resolve this problem, the patch add a KCONFIG_FILE parameter to handle such case. When KCONFIG_FILE is specified, hypervisor could build hypervisor with the specific configuration file. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 22:40:14 +08:00
ifneq ($(KCONFIG_FILE),)
ifneq ($(KCONFIG_FILE), $(wildcard $(KCONFIG_FILE)))
$(error KCONFIG_FILE: $(KCONFIG_FILE) does not exist)
endif
override KCONFIG_FILE := $(realpath $(KCONFIG_FILE))
else
override KCONFIG_FILE := $(T)/hypervisor/build/.config
endif
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
ifneq ($(BOARD)$(SCENARIO),)
ifneq ($(BOARD_FILE)$(SCENARIO_FILE),)
$(error BOARD/SCENARIO parameter could not coexist with BOARD_FILE/SCENARIO_FILE)
endif
endif
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
ifneq ($(TARGET_DIR),)
CFG_DIR := $(realpath $(TARGET_DIR))
ifeq ($(CFG_DIR),)
ifeq ($(BOARD_FILE)$(SCENARIO_FILE),)
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
$(error TARGET_DIR $(TARGET_DIR) does not exist)
endif
endif
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
override TARGET_DIR := $(abspath $(TARGET_DIR))
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
endif
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
ifneq ($(BOARD_FILE)$(SCENARIO_FILE),)
ifneq ($(BOARD_FILE), $(wildcard $(BOARD_FILE)))
$(error BOARD_FILE: $(BOARD_FILE) does not exist)
endif
ifneq ($(SCENARIO_FILE), $(wildcard $(SCENARIO_FILE)))
$(error SCENARIO_FILE: $(SCENARIO_FILE) does not exist)
endif
override BOARD_FILE := $(realpath $(BOARD_FILE))
override SCENARIO_FILE := $(realpath $(SCENARIO_FILE))
endif
ifeq ($(KCONFIG_FILE), $(wildcard $(KCONFIG_FILE)))
ifneq ($(BOARD)$(SCENARIO),)
Makefile: disable KCONFIG_FILE when build from xml The SCENARIO xml file already includes all information of KCONFIG file, use KCONFIG_FILE/SCENARIO_FILE parameter at same time would introduce conflict so this case should be invalid. Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-16 09:54:43 +08:00
$(error BOARD/SCENARIO parameter could not coexist with Kconfig file: $(KCONFIG_FILE))
endif
ifneq ($(BOARD_FILE)$(SCENARIO_FILE),)
$(error BOARD_FILE/SCENARIO_FILE parameter could not coexist with Kconfig file: $(KCONFIG_FILE))
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
endif
BOARD_IN_KCONFIG := $(shell grep CONFIG_BOARD= $(KCONFIG_FILE) | grep -v '\#' | awk -F '"' '{print $$2}')
ifeq ($(BOARD_IN_KCONFIG),)
$(error no BOARD info in KCONFIG_FILE: $(KCONFIG_FILE))
endif
Kconfig: change scenario variable type to string Basicly ACRN scenario is a configuration name for specific usage. By giving scenario name ACRN will load corresponding VM configurations to build the hypervisor. But customer might have their own scenario name, change the scenario type from choice to string is friendly to them since Kconfig source file change will not be needed. With this change, CONFIG_$(SCENARIO) will not exist in kconfig file and will be instead of CONFIG_SCENARIO, so the Makefile need to be changed accordingly; Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-13 09:47:26 +08:00
SCENARIO_IN_KCONFIG := $(shell grep CONFIG_SCENARIO= $(KCONFIG_FILE) | grep -v '\#' | awk -F '"' '{print $$2}')
Makefile: parameters check for board and scenario When user use make parameters to specify BOARD and SCENARIO, there might be some conflict because parameter of KCONFIG_FILE/BOARD_FILE/SCENARIO_FILE also includes BOARD/SCENARIO info. To simplify, we only alow below valid usages: 1. make <target> 2. make <target> KCONFIG_FILE=xxx 3. make <target> BOARD=xxx SCENARIO=xxx 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx Especially for case 1 that no any parameters are specified: a. If hypervisor/build/.config file which generated by "make menuconfig" exist, the .config file will be loaded as KCONFIG_FILE: i.e. equal: make <target> KCONFIG_FILE=hypervisor/build/.config b. If hypervisor/build/.config file does not exist, the default BOARD/SCENARIO will be loaded: i.e. equal: make <target> BOARD=$(BOARD) SCENARIO=$(SCENARIO) Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 23:53:05 +08:00
ifeq ($(SCENARIO_IN_KCONFIG),)
$(error no SCENARIO info in KCONFIG_FILE: $(KCONFIG_FILE))
endif
override BOARD := $(BOARD_IN_KCONFIG)
override SCENARIO := $(SCENARIO_IN_KCONFIG)
RELEASE := $(shell grep CONFIG_RELEASE=y $(KCONFIG_FILE) | grep -v '\#')
ifneq ($(RELEASE),)
override RELEASE := 1
endif
endif
Modify KBL-NUC/SDC for default build Tracked-On: #3968 Signed-off-by: wenlingz <wenling.zhang@intel.com>
2019-10-30 13:35:57 +08:00
BOARD ?= kbl-nuc-i7
Makefile: separate PLATFORM into BOARD+FIRMWARE Combination of BOARD and FIRMWARE is a more precious definition. And we decide PLATFORM_XXX based on FIRMWARE, remove relative one in board config. We reserve PLATFORM for backward compatibility. Tracked-On: #1995 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Yin Fengwei < fengwei.yin@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2018-12-11 16:00:56 +08:00
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
ifeq ($(BOARD), apl-nuc)
override BOARD := nuc6cayh
else ifeq ($(BOARD), kbl-nuc-i7)
override BOARD := nuc7i7dnb
endif
make: white-list SBL firmware boards The top-level Makefile white-lists BOARDs require to generate UEFI executable, but more UEFI BOARDs have been supported since then. As a result, the build instructions in existing documents may not be sufficient for those new BOARD targets, if the reader misses to supply the FIRMWARE variable while building the hypervisor. Instead of adding new UEFI BOARD types using the original long if-else statements, I'd like to propose to white-list SBL BOARD types, and add the new SBL BOARD types to the list while needed. Tracked-On: #3541 Signed-off-by: Tonny Tzeng <tonny.tzeng@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2019-08-06 19:46:31 +08:00
ifneq (,$(filter $(BOARD),apl-mrb))
FIRMWARE ?= sbl
else
FIRMWARE ?= uefi
Makefile: separate PLATFORM into BOARD+FIRMWARE Combination of BOARD and FIRMWARE is a more precious definition. And we decide PLATFORM_XXX based on FIRMWARE, remove relative one in board config. We reserve PLATFORM for backward compatibility. Tracked-On: #1995 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Yin Fengwei < fengwei.yin@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2018-12-11 16:00:56 +08:00
endif
HV: Make: remove sdc scenario build support The SDC scenario configurations will not be validated so remove it from build makefile; Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-16 12:27:22 +08:00
SCENARIO ?= industry
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
acrn: allow to specify the build output folder Usages: make O=<any folder> Signed-off-by: Jack Ren <jack.ren@intel.com>
2018-05-23 19:24:29 +08:00
O ?= build
ROOT_OUT := $(shell mkdir -p $(O);cd $(O);pwd)
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
HV_OUT := $(ROOT_OUT)/hypervisor
DM_OUT := $(ROOT_OUT)/devicemodel
HV:Acrn-hypvervisor Root Directory Clean-up and create misc/ folder for Acrn daemons, services and tools. This patch is to clean-up acrn-hypervisor root directory, targt only 5 folders under acrn-hypervisor:1.hypervisor,2.devicemodel,3.misc,4.doc,5.build Tracked-On: #3482 Signed-off-by: Terry Zou <terry.zou@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2019-07-29 12:21:54 +08:00
TOOLS_OUT := $(ROOT_OUT)/misc/tools
Build system: add target to build documentation This patch adds a new target to build the documentation from the top-level directory. Here is how to use it (from the top-level source directory): $ make doc Or $ make O=build-test doc To clean all documentation build artefacts, simply call $ make clean Or $ make O=build-test clean Calling 'make' with no arguments will *not* build the documentation by default. Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2018-06-12 17:38:43 +08:00
DOC_OUT := $(ROOT_OUT)/doc
DM: add tag info while no repo in release there is no git repo, which download from github release, however, acrn-dm -v will get tag info from this repo, in such case, the tag info was null. this patch will fix nul tag, which get it from CL mock build. Tracked-On: #676 Signed-off-by: Wei Liu <weix.w.liu@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com>
2018-08-06 10:09:27 +08:00
BUILD_VERSION ?=
BUILD_TAG ?=
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
HV_CFG_LOG = $(HV_OUT)/cfg.log
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
VM_CONFIGS_DIR = $(T)/misc/vm_configs
DEFCONFIG_FILE = scenarios/$(SCENARIO)/$(BOARD)/$(BOARD).config
makefile: cover menuconfig way to configure board/scenario We now have four methods to configure board and scenario when build acrn (sorted with priority): 1. Change them with "make menuconfig" in hypervisor directory 2. Give baord_file/scenario_file as make command parameters 3. Give BOARD/SCENARIO as make command parameters 4. Use BOARD/SCENARIO default value defined in Makefile file With this patch, we make sure we follow priority exactly. Tracked-On: #4067 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com> Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-11-10 09:05:41 +08:00
Makefile: support make from XML for new board Currently make hypervisor will depend on a $(BOARD).config file to load board defconfig which triggered by oldconfig process, this will block make from XMLs for a new board because $(BOARD).config never exist. This requires us to patch configuration for new board earlier than make oldconfig. Tracked-On: #4067 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-11-09 11:18:58 +08:00
export TOOLS_OUT BOARD SCENARIO FIRMWARE RELEASE
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
misc: totally remove misc folder misc now has a new home: https://github.com/intel/ioc-cbc-tools. The "Execstop" patch will be synced to new git tree soon. ioc-cbc-tools was just added to Clear Linux, and will be added to software-defined-cockpit bundle after this patch merged. Merging this patch may cause some IOC releated feature block until we get a new Clear Linux release. This is the switch window ... Signed-off-by: Alek Du <alek.du@intel.com>
2018-08-09 09:25:13 +08:00
.PHONY: all hypervisor devicemodel tools doc
all: hypervisor devicemodel tools
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
@cat $(HV_CFG_LOG)
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
Makefile: move .mk file to hv scripts folder The *.mk files under misc/acrn-config/library are all rules for hypervisor makefiles only, so move these files to hypervisor/scripts/makefile/ folder. The folder of acrn-config/library/ will be used to store python script lib only. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Terry Zou <terry.zou@intel.com>
2019-11-12 14:11:58 +08:00
include $(T)/hypervisor/scripts/makefile/cfg_update.mk
Makefile: support make from XML for new board Currently make hypervisor will depend on a $(BOARD).config file to load board defconfig which triggered by oldconfig process, this will block make from XMLs for a new board because $(BOARD).config never exist. This requires us to patch configuration for new board earlier than make oldconfig. Tracked-On: #4067 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-11-09 11:18:58 +08:00
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
#help functions to build acrn and install acrn/acrn symbols
define build_acrn
Kconfig: change scenario variable type to string Basicly ACRN scenario is a configuration name for specific usage. By giving scenario name ACRN will load corresponding VM configurations to build the hypervisor. But customer might have their own scenario name, change the scenario type from choice to string is friendly to them since Kconfig source file change will not be needed. With this change, CONFIG_$(SCENARIO) will not exist in kconfig file and will be instead of CONFIG_SCENARIO, so the Makefile need to be changed accordingly; Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-13 09:47:26 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE) clean
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE) defconfig
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE) oldconfig
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE)
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
endef
define install_acrn
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE) install
endef
define install_acrn_debug
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)-$(1)/$(2) BOARD=$(2) FIRMWARE=$(1) SCENARIO=$(3) RELEASE=$(RELEASE) install-debug
endef
Makefile: generate config patch in hypervisor/Makefile Previously we generate config patch based on config xml in toplevel Makefile, it brings two issues: 1. we could not generate xml configuration patch with hypervisor source only; 2. The github commit info of current code base which is defined in version.h will be overwritten by the new generated config patch, then the lost commit info would impact build identify and bug reproducing. This patch fixed these two issues. Besides, the patch also modify the logic of platform_acpi_info file existence judgement, which need to be depends on the acrn-config patch. Tracked-On: #3602 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-09-19 23:07:10 +08:00
hypervisor:
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
@if [ "$(BOARD_FILE)" != "" ] && [ -f $(BOARD_FILE) ] && [ "$(SCENARIO_FILE)" != "" ] && [ -f $(SCENARIO_FILE) ] && [ "$(TARGET_DIR)" = "" ]; then \
echo "No TARGET_DIR parameter is specified, the original configuration source is overwritten!";\
fi
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
$(MAKE) -C $(T)/hypervisor BOARD=$(BOARD) HV_OBJDIR=$(HV_OUT) BOARD_FILE=$(BOARD_FILE) SCENARIO_FILE=$(SCENARIO_FILE) TARGET_DIR=$(TARGET_DIR) defconfig;
$(MAKE) -C $(T)/hypervisor BOARD=$(BOARD) HV_OBJDIR=$(HV_OUT) BOARD_FILE=$(BOARD_FILE) SCENARIO_FILE=$(SCENARIO_FILE) TARGET_DIR=$(TARGET_DIR) oldconfig;
$(MAKE) -C $(T)/hypervisor BOARD=$(BOARD) HV_OBJDIR=$(HV_OUT) BOARD_FILE=$(BOARD_FILE) SCENARIO_FILE=$(SCENARIO_FILE) TARGET_DIR=$(TARGET_DIR)
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
@echo -e "\n\033[47;30mACRN Configuration Summary:\033[0m \nBOARD = $(BOARD)\t SCENARIO = $(SCENARIO)" > $(HV_CFG_LOG); \
Makefile: disable KCONFIG_FILE when build from xml The SCENARIO xml file already includes all information of KCONFIG file, use KCONFIG_FILE/SCENARIO_FILE parameter at same time would introduce conflict so this case should be invalid. Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-16 09:54:43 +08:00
echo -e "BUILD type = \c" >> $(HV_CFG_LOG); \
if [ "$(RELEASE)" = "0" ]; then echo -e "DEBUG" >> $(HV_CFG_LOG); else echo -e "RELEASE" >> $(HV_CFG_LOG); fi; \
Makefile: make hypervisor from specified Kconfig When user finish doing "make menuconfig", the .config file is saved in acrn-config/hypervisor/build/ by default. So current Makefile will check whether this customized .config file exists and then continue to do following make process. But this might not true in the real user case, user could put this customized .config file anywhere. To resolve this problem, the patch add a KCONFIG_FILE parameter to handle such case. When KCONFIG_FILE is specified, hypervisor could build hypervisor with the specific configuration file. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-16 22:40:14 +08:00
if [ -f $(KCONFIG_FILE) ]; then \
echo -e "Hypervisor configuration is based on:\n\tKconfig file:\t$(KCONFIG_FILE);" >> $(HV_CFG_LOG); \
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
fi; \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "Hypervisor configuration is based on:" >> $(HV_CFG_LOG); \
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
if [ "$(TARGET_DIR)" = "" ]; then \
if [ ! -f $(KCONFIG_FILE) ]; then \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "\tdefconfig file:\t\t\t$(VM_CONFIGS_DIR)/$(DEFCONFIG_FILE);" >> $(HV_CFG_LOG); \
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
fi; \
elif [ ! -f $(KCONFIG_FILE) ]; then \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "\tdefconfig file:\t\t\t$(TARGET_DIR)/$(DEFCONFIG_FILE);" >> $(HV_CFG_LOG); \
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
fi; \
echo -e "\tOthers are set by default in:\t$(T)/hypervisor/arch/x86/Kconfig;" >> $(HV_CFG_LOG); \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "VM configuration is based on:" >> $(HV_CFG_LOG); \
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
if [ "$(CONFIG_XML_ENABLED)" = "true" ]; then \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "\tBOARD File:\t\t$(BOARD_FILE);\n\t\tSCENARIO File:\t$(SCENARIO_FILE);" >> $(HV_CFG_LOG); \
elif [ "$(TARGET_DIR)" = "" ]; then \
echo -e "\tSource code at:\t\t\t$(VM_CONFIGS_DIR)" >> $(HV_CFG_LOG); \
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
else \
HV: Make: enable build for new configs layout The make command is same as old configs layout: under acrn-hypervisor folder: make hypervisor BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] under hypervisor folder: make BOARD=xxx SCENARIO=xxx [TARGET_DIR]=xxx [RELEASE=x] if BOARD/SCENARIO parameter is not specified, the default will be: BOARD=nuc7i7dnb SCENARIO=industry Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-15 16:40:24 +08:00
echo -e "\tSource code at:\t\t\t$(TARGET_DIR)" >> $(HV_CFG_LOG); \
HV: Make: simplify acpi info header file check Previously we have complicated check mechanism on platform_acpi_info.h which is supposed to be generated by acrn-config tool, but given the reality that all configurations should be generated by acrn-config before build acrn hypervisor, this check is not needed anymore. Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-16 13:01:30 +08:00
fi;
Makefile: print config summary at the end The BOARD and SCENARIO parameter of make hypervisor might be overridden by menuconfig file or BOARD/SCENARIO XML files in make process, also the $(BOARD)_acpi_info.h would be involved in build if exist, but user might not be aware of that because the message could be easily ignored from flooding logs. So give the configuration summary at the end of hypervisor build process would be helpful for end user. Tracked-On: #3779 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-12-09 12:13:49 +08:00
@cat $(HV_CFG_LOG)
Makefile: add a target to build sbl hypervisor To build with only one command the sbl and efi hypervisor a target was added which build the SBL hypervisor version. Now you can call "make all sbl-hypervisor" and "make install sbl-hypervisor-install" Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-24 17:39:59 +08:00
DM: adapt dm-monitor and acrnctl to use the helpers Adapt dm-monitor and acrnctl to use the helper functions and new message definitions in acrn_mngr.h. These jobs must be done in one commit to avoid build problems: 1. message transmission and callback registration code are moved to libacrn-mngr.a, so old functions in dm-monitor could be removed to make code clean; 2. remove unnecessary monior_msg.h; 3. minor changes to acrnctl accordingly. Reviewed-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Wang, Yu <yu1.wang@intel.com> signed-off-by: Yan Like <like.yan@intel.com> Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-05-30 02:16:56 +08:00
devicemodel: tools
acrn-dm: enable debug option for acrn-dm enable acrn-dm debug option via RELEASE=0(by default) Tracked-On: #2939 Reviewed-by: Minggui Cao <minggui.cao@intel.com> Signed-off-by: Wei Liu <weix.w.liu@intel.com> Acked-by: Yu Wang <yu1.wang@intel.com>
2019-04-16 10:59:25 +08:00
$(MAKE) -C $(T)/devicemodel DM_OBJDIR=$(DM_OUT) DM_BUILD_VERSION=$(BUILD_VERSION) DM_BUILD_TAG=$(BUILD_TAG) DM_ASL_COMPILER=$(ASL_COMPILER) RELEASE=$(RELEASE)
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
tools:
mkdir -p $(TOOLS_OUT)
HV:Acrn-hypvervisor Root Directory Clean-up and create misc/ folder for Acrn daemons, services and tools. This patch is to clean-up acrn-hypervisor root directory, targt only 5 folders under acrn-hypervisor:1.hypervisor,2.devicemodel,3.misc,4.doc,5.build Tracked-On: #3482 Signed-off-by: Terry Zou <terry.zou@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2019-07-29 12:21:54 +08:00
$(MAKE) -C $(T)/misc OUT_DIR=$(TOOLS_OUT) RELEASE=$(RELEASE)
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
Build system: add target to build documentation This patch adds a new target to build the documentation from the top-level directory. Here is how to use it (from the top-level source directory): $ make doc Or $ make O=build-test doc To clean all documentation build artefacts, simply call $ make clean Or $ make O=build-test clean Calling 'make' with no arguments will *not* build the documentation by default. Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2018-06-12 17:38:43 +08:00
doc:
Use $(MAKE) when recursing Using 'make' directly means that the jobserver environment variables don't get passed down, so sub-builds for example don't use -j. This is documented as the wrong thing to do: https://www.gnu.org/software/make/manual/html_node/MAKE-Variable.html#MAKE-Variable Use $(MAKE) instead, and compile times drastically improve: acrn-devicemodel do_compile -13.5s -89.6% 15.0s -> 1.6s Tracked-On: #2370 Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-01-17 05:35:20 +08:00
$(MAKE) -C $(T)/doc html BUILDDIR=$(DOC_OUT)
Build system: add target to build documentation This patch adds a new target to build the documentation from the top-level directory. Here is how to use it (from the top-level source directory): $ make doc Or $ make O=build-test doc To clean all documentation build artefacts, simply call $ make clean Or $ make O=build-test clean Calling 'make' with no arguments will *not* build the documentation by default. Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2018-06-12 17:38:43 +08:00
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
.PHONY: clean
clean:
HV:Acrn-hypvervisor Root Directory Clean-up and create misc/ folder for Acrn daemons, services and tools. This patch is to clean-up acrn-hypervisor root directory, targt only 5 folders under acrn-hypervisor:1.hypervisor,2.devicemodel,3.misc,4.doc,5.build Tracked-On: #3482 Signed-off-by: Terry Zou <terry.zou@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2019-07-29 12:21:54 +08:00
$(MAKE) -C $(T)/misc OUT_DIR=$(TOOLS_OUT) clean
Use $(MAKE) when recursing Using 'make' directly means that the jobserver environment variables don't get passed down, so sub-builds for example don't use -j. This is documented as the wrong thing to do: https://www.gnu.org/software/make/manual/html_node/MAKE-Variable.html#MAKE-Variable Use $(MAKE) instead, and compile times drastically improve: acrn-devicemodel do_compile -13.5s -89.6% 15.0s -> 1.6s Tracked-On: #2370 Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-01-17 05:35:20 +08:00
$(MAKE) -C $(T)/doc BUILDDIR=$(DOC_OUT) clean
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
rm -rf $(ROOT_OUT)
Makefile: support make with external configurations Customer might have specific folder where stores their own configurations for their customized scenario/board, so add TARGET_DIR parameter to support option that build hyprvisor with specified configurations. So valid usages are: (target = all | hypervisor) 1. make <target> 2. make <target> KCONFIG_FILE=xxx [TARGET_DIR=xxx] 3. make <target> BOARD=xxx SCENARIO=xxx [TARGET_DIR=xxx] 4. make <target> BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] 5. make <target> KCONFIG_FILE=xxx BOARD_FILE=xxx SCENARIO_FILE=xxx [TARGET_DIR=xxx] If TARGET_DIR parameter is not specified in make command, hypervisor will be built with board configurations under hypervisor/arch/x86/configs/ and scenario configurations under hypervisor/scenarios/. Moreover, the configurations would be overwritten if BOARD/SCENARIO files are specified in make command. If TARGET_DIR parameter is specified in make command, hypervisor will be built with configuration under that folder if no BOARD/SCENARIO files are specified. When BOARD/SCENARIO files are available in make command, the TARGET_DIR is used to store configurations that BOARD/SCENARIO file provided, i.e. Configurations in TARGET_DIR folder will be overwritten. Tracked-On: #4517 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-03-24 10:58:52 +08:00
rm -rf $(TARGET_DIR)
tools: acrn-crashlog: add service/config files and scripts This patch adds the service files, config files and script to run automatically at boot. And it adds install/uninstall part in Makefile. Compatiblity code for libsystemd.so and libsystemd-journal.so is added in Makefile also. Signed-off-by: Jin Zhi <zhi.jin@intel.com> Signed-off-by: CHEN Gang <gang.c.chen@intel.com> Reviewed-by: Zhang Yanmin <yanmin.zhang@intel.com> Reviewed-by: Liu Chuansheng <chuansheng.liu@intel.com> Reviewed-by: Zhao Yakui <yakui.zhao@intel.com> Reviewed-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> Acked-by: Eddie Dong <Eddie.dong@intel.com>
2018-05-18 16:38:19 +08:00
Makefile: implement make install The make install target was missing. This commits adds the intall target which uses the install target from subprojects. Also a make install target was created in each tool program. Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-17 03:21:45 +08:00
.PHONY: install
misc: totally remove misc folder misc now has a new home: https://github.com/intel/ioc-cbc-tools. The "Execstop" patch will be synced to new git tree soon. ioc-cbc-tools was just added to Clear Linux, and will be added to software-defined-cockpit bundle after this patch merged. Merging this patch may cause some IOC releated feature block until we get a new Clear Linux release. This is the switch window ... Signed-off-by: Alek Du <alek.du@intel.com>
2018-08-09 09:25:13 +08:00
install: hypervisor-install devicemodel-install tools-install
add a makefile under project root directory it can be used as following: make ==> to make hypervisor & devicemodel & tools also modify tools makefile to support out-dir setting. Signed-off-by: Minggui Cao <minggui.cao@intel.com> Reviewed-by: Jack Ren <jack.ren@intel.com>
2018-05-15 09:09:20 +08:00
Makefile: generate config patch in hypervisor/Makefile Previously we generate config patch based on config xml in toplevel Makefile, it brings two issues: 1. we could not generate xml configuration patch with hypervisor source only; 2. The github commit info of current code base which is defined in version.h will be overwritten by the new generated config patch, then the lost commit info would impact build identify and bug reproducing. This patch fixed these two issues. Besides, the patch also modify the logic of platform_acpi_info file existence judgement, which need to be depends on the acrn-config patch. Tracked-On: #3602 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-09-19 23:07:10 +08:00
hypervisor-install:
Makefile: Refine Makefile to generate both industry and sdc images We are trying to add both industry and sdc images to CL build. To maintain the build interface unchanged (no change from CL side), we extend the build command to generate the different target images. To identity different images, we use rule: $(HV_FILE).$(BOARD).$(FIRMWARE).$(SCENARIO) as target image file name. Tracked-On: #3593 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-08-14 11:27:21 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT) BOARD=$(BOARD) FIRMWARE=$(FIRMWARE) SCENARIO=$(SCENARIO) RELEASE=$(RELEASE) install
Makefile: implement make install The make install target was missing. This commits adds the intall target which uses the install target from subprojects. Also a make install target was created in each tool program. Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-17 03:21:45 +08:00
Makefile: generate config patch in hypervisor/Makefile Previously we generate config patch based on config xml in toplevel Makefile, it brings two issues: 1. we could not generate xml configuration patch with hypervisor source only; 2. The github commit info of current code base which is defined in version.h will be overwritten by the new generated config patch, then the lost commit info would impact build identify and bug reproducing. This patch fixed these two issues. Besides, the patch also modify the logic of platform_acpi_info file existence judgement, which need to be depends on the acrn-config patch. Tracked-On: #3602 Signed-off-by: Victor Sun <victor.sun@intel.com>
2019-09-19 23:07:10 +08:00
hypervisor-install-debug:
Makefile: Refine Makefile to generate both industry and sdc images We are trying to add both industry and sdc images to CL build. To maintain the build interface unchanged (no change from CL side), we extend the build command to generate the different target images. To identity different images, we use rule: $(HV_FILE).$(BOARD).$(FIRMWARE).$(SCENARIO) as target image file name. Tracked-On: #3593 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-08-14 11:27:21 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT) BOARD=$(BOARD) FIRMWARE=$(FIRMWARE) SCENARIO=$(SCENARIO) RELEASE=$(RELEASE) install-debug
Makefile: add rules for installing debug information Add rules for installing debug information. Tracked-On: #2344 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2019-01-22 11:12:53 +08:00
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
kbl-nuc-i7-uefi-industry:
Kconfig: change scenario variable type to string Basicly ACRN scenario is a configuration name for specific usage. By giving scenario name ACRN will load corresponding VM configurations to build the hypervisor. But customer might have their own scenario name, change the scenario type from choice to string is friendly to them since Kconfig source file change will not be needed. With this change, CONFIG_$(SCENARIO) will not exist in kconfig file and will be instead of CONFIG_SCENARIO, so the Makefile need to be changed accordingly; Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-13 09:47:26 +08:00
$(call build_acrn,uefi,nuc7i7dnb,industry)
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid:
Kconfig: change scenario variable type to string Basicly ACRN scenario is a configuration name for specific usage. By giving scenario name ACRN will load corresponding VM configurations to build the hypervisor. But customer might have their own scenario name, change the scenario type from choice to string is friendly to them since Kconfig source file change will not be needed. With this change, CONFIG_$(SCENARIO) will not exist in kconfig file and will be instead of CONFIG_SCENARIO, so the Makefile need to be changed accordingly; Tracked-On: #4616 Signed-off-by: Victor Sun <victor.sun@intel.com>
2020-04-13 09:47:26 +08:00
$(call build_acrn,uefi,apl-up2,hybrid)
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
HV: Make: remove sdc scenario build support The SDC scenario configurations will not be validated so remove it from build makefile; Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-16 12:27:22 +08:00
sbl-hypervisor: kbl-nuc-i7-uefi-industry \
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
kbl-nuc-i7-uefi-industry-install:
Modify KBL-NUC/SDC for default build Tracked-On: #3968 Signed-off-by: wenlingz <wenling.zhang@intel.com>
2019-10-30 13:35:57 +08:00
$(call install_acrn,uefi,nuc7i7dnb,industry)
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid-install:
$(call install_acrn,uefi,apl-up2,hybrid)
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
HV: Make: remove sdc scenario build support The SDC scenario configurations will not be validated so remove it from build makefile; Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-16 12:27:22 +08:00
sbl-hypervisor-install: kbl-nuc-i7-uefi-industry-install \
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid-install
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
kbl-nuc-i7-uefi-industry-install-debug:
Modify KBL-NUC/SDC for default build Tracked-On: #3968 Signed-off-by: wenlingz <wenling.zhang@intel.com>
2019-10-30 13:35:57 +08:00
$(call install_acrn_debug,uefi,nuc7i7dnb,industry)
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid-install-debug:
$(call install_acrn_debug,uefi,apl-up2,hybrid)
Makefile: Add acrn build/install functions To remove several duplicated Makefile cmdline, introduce the functions to build/install acrn. If we need to add new build to sbl-hypervisor (which is used by integration team), we only need to define a new target and call acrn build/install functions with correct parameters. And then make sbl-hypervisor depend on that new target. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-09-27 17:15:36 +08:00
HV: Make: remove sdc scenario build support The SDC scenario configurations will not be validated so remove it from build makefile; Tracked-On: #5077 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2020-07-16 12:27:22 +08:00
sbl-hypervisor-install-debug: kbl-nuc-i7-uefi-industry-install-debug \
Makefile: Add new build target for apl-up2/uefi/hybrid Add new build target for hybrid mode with uefi on platform apl-up2. Also break long dependency target line to short one. Tracked-On: #3779 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
2019-10-08 13:29:55 +08:00
apl-up2-uefi-hybrid-install-debug
Makefile: add rules for installing debug information Add rules for installing debug information. Tracked-On: #2344 Signed-off-by: Tw <wei.tan@intel.com> Reviewed-by: Binbin Wu <binbin.wu@intel.com>
2019-01-22 11:12:53 +08:00
Makefile: implement make install The make install target was missing. This commits adds the intall target which uses the install target from subprojects. Also a make install target was created in each tool program. Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-17 03:21:45 +08:00
devicemodel-install:
Use $(MAKE) when recursing Using 'make' directly means that the jobserver environment variables don't get passed down, so sub-builds for example don't use -j. This is documented as the wrong thing to do: https://www.gnu.org/software/make/manual/html_node/MAKE-Variable.html#MAKE-Variable Use $(MAKE) instead, and compile times drastically improve: acrn-devicemodel do_compile -13.5s -89.6% 15.0s -> 1.6s Tracked-On: #2370 Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-01-17 05:35:20 +08:00
$(MAKE) -C $(T)/devicemodel DM_OBJDIR=$(DM_OUT) install
Makefile: implement make install The make install target was missing. This commits adds the intall target which uses the install target from subprojects. Also a make install target was created in each tool program. Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-17 03:21:45 +08:00
Makefile: fix typos and style Remove the trailing ";" and "\" and fix a typo in install. Signed-off-by: Miguel Bernal Marin <miguel.bernal.marin@linux.intel.com>
2018-05-17 06:59:53 +08:00
tools-install:
HV:Acrn-hypvervisor Root Directory Clean-up and create misc/ folder for Acrn daemons, services and tools. This patch is to clean-up acrn-hypervisor root directory, targt only 5 folders under acrn-hypervisor:1.hypervisor,2.devicemodel,3.misc,4.doc,5.build Tracked-On: #3482 Signed-off-by: Terry Zou <terry.zou@intel.com> Acked-by: Eddie Dong <eddie.dong@intel.com>
2019-07-29 12:21:54 +08:00
$(MAKE) -C $(T)/misc OUT_DIR=$(TOOLS_OUT) RELEASE=$(RELEASE) install