d461391b31
The new rcw.py script is python3-only, but we can use either the system-provided python3, or the one we build with host-python3 if the system does not have it already. It turns out, also, that rcw.py is using #!/usr/bin/env python3, so it will easily find it from $PATH, so we export it in the environment. Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net> [yann.morin.1998@free.fr: - set the proper PATH in the envioronment - do not explicitly call python3, defer to /usr/bin/env in the script - add an accompagnying comment - rewrite commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
68 lines
2.0 KiB
Makefile
68 lines
2.0 KiB
Makefile
################################################################################
|
|
#
|
|
# rcw
|
|
#
|
|
################################################################################
|
|
|
|
RCW_VERSION = LSDK-19.09
|
|
RCW_SITE = https://source.codeaurora.org/external/qoriq/qoriq-components/rcw
|
|
RCW_SITE_METHOD = git
|
|
RCW_LICENSE = BSD-3-Clause
|
|
RCW_LICENSE_FILES = LICENSE
|
|
|
|
HOST_RCW_DEPENDENCIES = $(BR2_PYTHON3_HOST_DEPENDENCY)
|
|
|
|
RCW_FILES = $(call qstrip,$(BR2_PACKAGE_HOST_RCW_CUSTOM_PATH))
|
|
|
|
ifneq ($(RCW_FILES),)
|
|
RCW_INCLUDES = $(filter-out %.rcw,$(RCW_FILES))
|
|
# Get the name of the custom rcw file from the custom list
|
|
RCW_PROJECT = $(notdir $(filter %.rcw,$(RCW_FILES)))
|
|
|
|
# Error if there are no or more than one .rcw file
|
|
ifeq ($(BR_BUILDING),y)
|
|
ifneq ($(words $(RCW_PROJECT)),1)
|
|
$(error BR2_PACKAGE_HOST_RCW_CUSTOM_PATH must have exactly one .rcw file)
|
|
endif
|
|
endif
|
|
|
|
ifneq ($(RCW_INCLUDES),)
|
|
define HOST_RCW_ADD_CUSTOM_RCW_INCLUDES
|
|
mkdir -p $(@D)/custom_board
|
|
cp -f $(RCW_INCLUDES) $(@D)/custom_board
|
|
endef
|
|
HOST_RCW_POST_PATCH_HOOKS += HOST_RCW_ADD_CUSTOM_RCW_INCLUDES
|
|
endif
|
|
|
|
define HOST_RCW_ADD_CUSTOM_RCW_FILES
|
|
mkdir -p $(@D)/custom_board/rcw
|
|
cp -f $(filter %.rcw,$(RCW_FILES)) $(@D)/custom_board/rcw
|
|
endef
|
|
HOST_RCW_POST_PATCH_HOOKS += HOST_RCW_ADD_CUSTOM_RCW_FILES
|
|
|
|
# rcw.py is a python3-only script, and we can be using either the
|
|
# system-provided python3, or our own built with host-python3.
|
|
# Fortunately, rcw.py uses #!/usr/bin/env python3, so it will
|
|
# easily find it from PATH.
|
|
define HOST_RCW_BUILD_CMDS
|
|
PATH=$(BR_PATH) \
|
|
$(@D)/rcw.py \
|
|
-i $(@D)/custom_board/rcw/$(RCW_PROJECT) \
|
|
-I $(@D)/custom_board -o $(@D)/PBL.bin
|
|
endef
|
|
|
|
define HOST_RCW_INSTALL_DELIVERY_FILE
|
|
$(INSTALL) -D -m 0644 $(@D)/PBL.bin $(BINARIES_DIR)/PBL.bin
|
|
endef
|
|
endif
|
|
|
|
# Copy source files and script into $(HOST_DIR)/share/rcw/ so a developer
|
|
# could use a post image or SDK to build/install PBL files.
|
|
define HOST_RCW_INSTALL_CMDS
|
|
mkdir -p $(HOST_DIR)/share/rcw
|
|
cp -a $(@D)/* $(HOST_DIR)/share/rcw
|
|
$(HOST_RCW_INSTALL_DELIVERY_FILE)
|
|
endef
|
|
|
|
$(eval $(host-generic-package))
|