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

161 lines
5.1 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
hv: set SHELL in top-level Makefile Explicitly set the SHELL variable in the top-level Makefile. This ensures that 'echo -e' as used in the Makefile behaves correctly on various systems. It does require /bin/bash to be present but that is probably true on many systems. Tracked-On: #5588 Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2020-12-07 18:16:23 +08:00
# Explicitly set the shell to be used
SHELL := /bin/bash
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: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
ifdef TARGET_DIR
$(warning TARGET_DIR is obsoleted because generated configuration files are now stored in the build directory)
endif
ifdef KCONFIG_FILE
$(warning KCONFIG_FILE is no longer supported)
$(error To specify the target board and scenario, define BOARD/SCENARIO variables on the command line)
endif
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: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
# BOARD/SCENARIO/BOARD_FILE/SCENARIO_FILE parameters sanity check:
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
#
# Only below usages are VALID: (target = all | hypervisor)
# 1. make <target>
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
# 2. make <target> BOARD=xxx SCENARIO=xxx
# 3. make <target> BOARD_FILE=xxx SCENARIO_FILE=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
#
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
# For case 1 that no any parameters are specified, the default BOARD/SCENARIO will be loaded:
# i.e. equal: make <target> BOARD=kbl-nuc-i7 SCENARIO=industry
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
#
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
# For case 2/3, configurations are from XML files and saved to HV_OUT
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
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
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
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
override BOARD := $(realpath $(BOARD_FILE))
override SCENARIO := $(realpath $(SCENARIO_FILE))
else
# BOARD/SCENARIO pointing to XML files must be converted to absolute paths before being passed to hypervisor/Makefile
# because paths relative to acrn-hypervisor/ are typically invalid when relative to acrn-hypervisor/Makefile
ifneq ($(realpath $(BOARD)),)
override BOARD := $(realpath $(BOARD))
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
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
ifneq ($(realpath $(SCENARIO)),)
override SCENARIO := $(realpath $(SCENARIO))
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
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
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
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: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
export TOOLS_OUT BOARD SCENARIO 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: 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
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)/$(1) clean
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)/$(1) BOARD=$(1) SCENARIO=$(2) 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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)/$(1) BOARD=$(1) SCENARIO=$(2) RELEASE=$(RELEASE) 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
endef
define install_acrn_debug
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT)/$(1) BOARD=$(1) SCENARIO=$(2) RELEASE=$(RELEASE) install-debug
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
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: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
$(MAKE) -C $(T)/hypervisor BOARD=$(BOARD) SCENARIO=$(SCENARIO) HV_OBJDIR=$(HV_OUT) RELEASE=$(RELEASE)
Revert "hv: fix formatting for cfg.log output" This reverts commit e2590d88aa3e1c72dc6473eadc83312412a604b3. It introdcues a regression for systems that have '/bin/sh' pointing at '/bin/bash'. Tracked-On: #5588 Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2020-12-07 18:12:44 +08:00
@echo -e "\n\033[47;30mACRN Configuration Summary:\033[0m \nBOARD = $(BOARD)\t SCENARIO = $(SCENARIO)" > $(HV_CFG_LOG); \
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; \
echo -e "VM configuration is based on:" >> $(HV_CFG_LOG); \
Makefile: remove rules related to Kconfig and TARGET_DIR With Kconfig being removed from the configuration process and configuration files generated in build directories, we no longer need KCONFIG_FILE or TARGET_DIR in the top-level Makefile. This patch removes rules that infer BOARD/SCENARIO from Kconfig files or specify where generated configuration files are saved. A warning is generated if a user defines TARGET_DIR while the build can proceed normally. An error is raised if a user defines KCONFIG_FILE. v2: * BOARD/SCENARIO now accept paths relative to where Makefile resides in Tracked-On: #5644 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
2021-01-14 14:04:48 +08:00
echo -e "\tSource code at:\t\t\t$(HV_OUT)/configs" >> $(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
@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)
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: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT) BOARD=$(BOARD) 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: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
$(MAKE) -C $(T)/hypervisor HV_OBJDIR=$(HV_OUT) BOARD=$(BOARD) 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: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
kbl-nuc-i7-industry:
$(call build_acrn,nuc7i7dnb,industry)
apl-up2-hybrid:
$(call build_acrn,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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
sbl-hypervisor: kbl-nuc-i7-industry \
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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
kbl-nuc-i7-industry-install:
$(call install_acrn,nuc7i7dnb,industry)
apl-up2-hybrid-install:
$(call install_acrn,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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
sbl-hypervisor-install: kbl-nuc-i7-industry-install \
apl-up2-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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
kbl-nuc-i7-industry-install-debug:
$(call install_acrn_debug,nuc7i7dnb,industry)
apl-up2-hybrid-install-debug:
$(call install_acrn_debug,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
Makefile: remove FIRMWARE variable from Makefile Since now we support direct boot only, we don't have to use FIRMWARE variable to differentiate between sbl/GRUB and UEFI boot. After this change: - "FIRMWARE=sbl/uefi" should be removed from make commands. - the firmware name is removed from the installed ACRN image. For example, acrn.apl-up2.sbl.sdc.32.out will be changed to acrn.apl-up2.sdc.32.out. Tracked-On: #5197 Signed-off-by: Zide Chen <zide.chen@intel.com>
2020-08-24 13:21:02 +08:00
sbl-hypervisor-install-debug: kbl-nuc-i7-industry-install-debug \
apl-up2-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