genode/repos/ports/lib/mk/virtualbox5.mk

include $(REP_DIR)/lib/mk/virtualbox5-common.inc

LIBS  += stdcxx

SRC_CC = sup.cc sup_vmm.cc

INC_DIR += $(call select_from_repositories,src/lib/libc)

INC_DIR += $(VIRTUALBOX_DIR)/VBoxAPIWrap

INC_DIR += $(VBOX_DIR)/Main/xml
INC_DIR += $(VBOX_DIR)/Main/include
INC_DIR += $(VBOX_DIR)/VMM/include
INC_DIR += $(REP_DIR)/src/virtualbox5
INC_DIR += $(REP_DIR)/src/virtualbox5/frontend

vpath sup_vmm.cc $(REP_DIR)/src/virtualbox5/generic
vpath sup.cc     $(REP_DIR)/src/virtualbox5/generic

CC_CXX_WARN_STRICT =
vbox5: unified build dir adjustments Issue #2338 2017-01-31 14:13:58 +00:00			`include $(REP_DIR)/lib/mk/virtualbox5-common.inc`

			`LIBS += stdcxx`

vbox5: use vm_session interface Issue #3111 2019-05-06 08:34:47 +00:00			`SRC_CC = sup.cc sup_vmm.cc`
vbox5: unified build dir adjustments Issue #2338 2017-01-31 14:13:58 +00:00
			`INC_DIR += $(call select_from_repositories,src/lib/libc)`
vbox5: update to 5.1.14 - use more upstream hm code - add call to memory check as done in vbox4 - add in principle all vbox devices and drivers - avoid null pointer during VM startup (patch reported to vbox-devel list) - avoid endless loop in usb root hub Issue #2338 2017-01-31 15:10:52 +00:00
			`INC_DIR += $(VIRTUALBOX_DIR)/VBoxAPIWrap`

vbox5: unified build dir adjustments Issue #2338 2017-01-31 14:13:58 +00:00			`INC_DIR += $(VBOX_DIR)/Main/xml`
			`INC_DIR += $(VBOX_DIR)/Main/include`
			`INC_DIR += $(VBOX_DIR)/VMM/include`
Remove virtualbox 4 vmm Fixes #3141 2019-02-11 13:38:15 +00:00			`INC_DIR += $(REP_DIR)/src/virtualbox5`
vbox5: unified build dir adjustments Issue #2338 2017-01-31 14:13:58 +00:00			`INC_DIR += $(REP_DIR)/src/virtualbox5/frontend`

vbox5: use vm_session interface Issue #3111 2019-05-06 08:34:47 +00:00			`vpath sup_vmm.cc $(REP_DIR)/src/virtualbox5/generic`
			`vpath sup.cc $(REP_DIR)/src/virtualbox5/generic`
Exclude higher-level repos from strict warnings This is a follow-up commit to "Increase default warning level", which overrides Genode's new default warning level for targets contained in higher-level repositories. By explicitly whitelisting all those targets, we can selectively adjust them to the new strictness over time - by looking out for 'CC_CXX_WARN_STRICT' in the target description files. Issue #465 2018-01-03 17:40:54 +00:00
			`CC_CXX_WARN_STRICT =`