2016-12-05 13:12:19 -06:00
|
|
|
include $(PLATFORM_PATH)/sdk.mk
|
|
|
|
|
include $(PLATFORM_PATH)/fw.mk
|
|
|
|
|
include $(PLATFORM_PATH)/mft.mk
|
|
|
|
|
include $(PLATFORM_PATH)/mlnx-sai.mk
|
|
|
|
|
include $(PLATFORM_PATH)/hw-management.mk
|
2019-02-13 07:21:07 -06:00
|
|
|
include $(PLATFORM_PATH)/mlnx-platform-api.mk
|
2016-12-05 13:12:19 -06:00
|
|
|
include $(PLATFORM_PATH)/docker-syncd-mlnx.mk
|
2017-03-24 20:36:56 -05:00
|
|
|
include $(PLATFORM_PATH)/docker-syncd-mlnx-rpc.mk
|
2018-11-14 03:15:31 -06:00
|
|
|
include $(PLATFORM_PATH)/docker-saiserver-mlnx.mk
|
2017-02-01 00:06:12 -06:00
|
|
|
include $(PLATFORM_PATH)/one-image.mk
|
2017-03-28 13:32:58 -05:00
|
|
|
include $(PLATFORM_PATH)/libsaithrift-dev.mk
|
2018-12-04 12:11:24 -06:00
|
|
|
include $(PLATFORM_PATH)/mlnx-ffb.mk
|
2019-01-17 16:41:32 -06:00
|
|
|
include $(PLATFORM_PATH)/issu-version.mk
|
2020-04-13 10:13:19 -05:00
|
|
|
include $(PLATFORM_PATH)/mlnx-onie-fw-update.mk
|
|
|
|
|
include $(PLATFORM_PATH)/mlnx-ssd-fw-update.mk
|
2023-02-02 02:07:03 -06:00
|
|
|
include $(PLATFORM_PATH)/bios.mk
|
2016-12-05 13:12:19 -06:00
|
|
|
|
2017-03-03 10:43:22 -06:00
|
|
|
SONIC_ALL += $(SONIC_ONE_IMAGE) \
|
2017-08-01 15:51:10 -05:00
|
|
|
$(DOCKER_FPM)
|
2016-12-05 13:12:19 -06:00
|
|
|
|
2020-07-03 00:03:50 -05:00
|
|
|
# Inject mlnx sai into syncd
|
|
|
|
|
$(SYNCD)_DEPENDS += $(MLNX_SAI)
|
[build]: wait for conflicts package to be uninstalled (#5039)
when parallel build is enabled, both docker-fpm-frr and docker-syncd-brcm
is built at the same time, docker-fpm-frr requires swss which requires to
install libsaivs-dev. docker-syncd-brcm requires syncd package which requires
to install libsaibcm-dev.
since libsaivs-dev and libsaibcm-dev install the sai header in the same
location, these two packages cannot be installed at the same time. Therefore,
we need to serialize the build between these two packages. Simply uninstall
the conflict package is not enough to solve this issue. The correct solution
is to have one package wait for another package to be uninstalled.
For example, if syncd is built first, then it will install libsaibcm-dev.
Meanwhile, if the swss build job starts and tries to install libsaivs-dev,
it will first try to query if libsaibcm-dev is installed or not. if it is
installed, then it will wait until libsaibcm-dev is uninstalled. After syncd
job is finished, it will uninstall libsaibcm-dev and swss build job will be
unblocked.
To solve this issue, _UNINSTALLS is introduced to uninstall a package that
is no longer needed and to allow blocked job to continue.
Signed-off-by: Guohan Lu <lguohan@gmail.com>
2020-07-27 12:46:20 -05:00
|
|
|
$(SYNCD)_UNINSTALLS += $(MLNX_SAI)
|
|
|
|
|
|
2019-07-06 16:55:31 -05:00
|
|
|
ifeq ($(ENABLE_SYNCD_RPC),y)
|
2020-07-03 00:03:50 -05:00
|
|
|
$(SYNCD)_DEPENDS += $(LIBSAITHRIFT_DEV)
|
2019-07-06 16:55:31 -05:00
|
|
|
endif
|
2016-12-05 13:12:19 -06:00
|
|
|
|
|
|
|
|
# Runtime dependency on mlnx sai is set only for syncd
|
|
|
|
|
$(SYNCD)_RDEPENDS += $(MLNX_SAI)
|
2019-06-14 19:38:24 -05:00
|
|
|
|
|
|
|
|
# Inject mlnx sdk libs to platform monitor
|
|
|
|
|
$(DOCKER_PLATFORM_MONITOR)_DEPENDS += $(APPLIBS) $(SX_COMPLIB) $(SXD_LIBS) $(SX_GEN_UTILS) $(PYTHON_SDK_API) $(APPLIBS_DEV) $(SX_COMPLIB_DEV) $(SXD_LIBS_DEV) $(SX_GEN_UTILS_DEV)
|
2020-12-13 13:35:39 -06:00
|
|
|
|
|
|
|
|
export SONIC_BUFFER_MODEL=dynamic
|
