mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-08 05:43:53 +00:00
3789c3c000
Since the introduction of the toolchain detection framework into the build system, we have done determination and identification of the toolchain(s) used for the build at the initialization of the build system. This incurs a large cost to the build every time - for every toolchain that has been requested by the current makefile, we try to identify each tool in the list of known tool classes, even if that tool doesn't actually see any use. For the clean and check-like targets we worked around this by disabling most of the toolchains if we detect these targets, but this is inflexible and not very reliable, and it still means that when building normal targets we are incurring that cost for all tools whether they are used or not. This change instead modifies the toolchain detection framework to only initialize a tool for a given toolchain when it is first used. This does mean that we can no longer warn about an incorrectly-configured toolchain at the beginning of build system invocation, but it has the advantage of substantially reducing build time and the complexity of *using* the framework (at the cost of an increase in complexity in the framework itself). Change-Id: I7f3d06b2eb58c1b26a846791a13b0037f32c8013 Signed-off-by: Chris Kay <chris.kay@arm.com>
81 lines
2.2 KiB
Makefile
81 lines
2.2 KiB
Makefile
#
|
|
# Copyright (c) 2024, Arm Limited. All rights reserved.
|
|
# Copyright (c) 2019-2022, Linaro Limited. All rights reserved.
|
|
#
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
#
|
|
|
|
BUILD_INFO ?= 1
|
|
DEBUG := 0
|
|
ENCTOOL ?= encrypt_fw${BIN_EXT}
|
|
BINARY := $(notdir ${ENCTOOL})
|
|
OPENSSL_DIR := /usr
|
|
|
|
MAKE_HELPERS_DIRECTORY := ../../make_helpers/
|
|
include ${MAKE_HELPERS_DIRECTORY}build_macros.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}build_env.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}common.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}defaults.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}toolchain.mk
|
|
|
|
OBJECTS := src/encrypt.o \
|
|
src/cmd_opt.o \
|
|
src/main.o
|
|
|
|
HOSTCCFLAGS := -Wall -std=c99
|
|
|
|
# Select OpenSSL version flag according to the OpenSSL build selected
|
|
# from setting the OPENSSL_DIR path.
|
|
$(eval $(call SELECT_OPENSSL_API_VERSION))
|
|
|
|
ifeq (${DEBUG},1)
|
|
HOSTCCFLAGS += -g -O0 -DDEBUG -DLOG_LEVEL=40
|
|
else
|
|
ifeq (${BUILD_INFO},1)
|
|
HOSTCCFLAGS += -O2 -DLOG_LEVEL=20
|
|
else
|
|
HOSTCCFLAGS += -O2 -DLOG_LEVEL=10
|
|
endif
|
|
endif
|
|
|
|
HOSTCCFLAGS += ${DEFINES}
|
|
# USING_OPENSSL3 flag will be added to the HOSTCCFLAGS variable with the proper
|
|
# computed value.
|
|
HOSTCCFLAGS += -DUSING_OPENSSL3=$(USING_OPENSSL3)
|
|
|
|
|
|
# Make soft links and include from local directory otherwise wrong headers
|
|
# could get pulled in from firmware tree.
|
|
INC_DIR := -I ./include -I ../../include/tools_share -I ${OPENSSL_DIR}/include
|
|
|
|
# Include library directories where OpenSSL library files are located.
|
|
# For a normal installation (i.e.: when ${OPENSSL_DIR} = /usr or
|
|
# /usr/local), binaries are located under the ${OPENSSL_DIR}/lib/
|
|
# directory. However, for a local build of OpenSSL, the built binaries are
|
|
# located under the main project directory (i.e.: ${OPENSSL_DIR}, not
|
|
# ${OPENSSL_DIR}/lib/).
|
|
LIB_DIR := -L ${OPENSSL_DIR}/lib -L ${OPENSSL_DIR}
|
|
LIB := -lssl -lcrypto
|
|
|
|
.PHONY: all clean realclean --openssl
|
|
|
|
all: --openssl ${BINARY}
|
|
|
|
${BINARY}: ${OBJECTS} Makefile
|
|
$(s)echo " HOSTLD $@"
|
|
$(q)$(host-cc) ${OBJECTS} ${LIB_DIR} ${LIB} -o $@
|
|
|
|
%.o: %.c
|
|
$(s)echo " HOSTCC $<"
|
|
$(q)$(host-cc) -c ${HOSTCCFLAGS} ${INC_DIR} $< -o $@
|
|
|
|
--openssl:
|
|
ifeq ($(DEBUG),1)
|
|
$(s)echo "Selected OpenSSL version: ${OPENSSL_CURRENT_VER}"
|
|
endif
|
|
|
|
clean:
|
|
$(call SHELL_DELETE_ALL,${OBJECTS})
|
|
|
|
realclean: clean
|
|
$(call SHELL_DELETE,${BINARY})
|