mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-16 01:24:27 +00:00
cc277de816
This change refactors how we identify the toolchain, with the ultimate
aim of eventually cleaning up the various mechanisms that we employ to
configure default tools, identify the tools in use, and configure
toolchain flags.
To do this, we introduce three new concepts in this change:
- Toolchain identifiers,
- Tool class identifiers, and
- Tool identifiers.
Toolchain identifiers identify a configurable chain of tools targeting
one platform/machine/architecture. Today, these are:
- The host machine, which receives the `host` identifier,
- The AArch32 architecture, which receives the `aarch32` identifier, and
- The AArch64 architecture, which receivs the `aarch64` identifier.
The tools in a toolchain may come from different vendors, and are not
necessarily expected to come from one single toolchain distribution. In
most cases it is perfectly valid to mix tools from different toolchain
distributions, with some exceptions (notably, link-time optimization
generally requires the compiler and the linker to be aligned).
Tool class identifiers identify a class (or "role") of a tool. C
compilers, assemblers and linkers are all examples of tool classes.
Tool identifiers identify a specific tool recognized and supported by
the build system. Every tool that can make up a part of a toolchain must
receive a tool identifier.
These new identifiers can be used to retrieve information about the
toolchain in a more standardized fashion.
For example, logic in a Makefile that should only execute when the C
compiler is GNU GCC can now check the tool identifier for the C compiler
in the relevant toolchain:
ifeq ($($(ARCH)-cc-id),gnu-gcc)
...
endif
Change-Id: Icc23e43aaa32f4fd01d8187c5202f5012a634e7c
Signed-off-by: Chris Kay <chris.kay@arm.com>
113 lines
2.9 KiB
Makefile
113 lines
2.9 KiB
Makefile
#
|
|
# Copyright (c) 2015-2024, Arm Limited and Contributors. All rights reserved.
|
|
#
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
#
|
|
|
|
PLAT := none
|
|
V ?= 0
|
|
DEBUG := 0
|
|
CRTTOOL ?= cert_create${BIN_EXT}
|
|
BINARY := $(notdir ${CRTTOOL})
|
|
COT := tbbr
|
|
|
|
toolchains := host
|
|
|
|
MAKE_HELPERS_DIRECTORY := ../../make_helpers/
|
|
include ${MAKE_HELPERS_DIRECTORY}build_macros.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}build_env.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}defaults.mk
|
|
include ${MAKE_HELPERS_DIRECTORY}toolchain.mk
|
|
|
|
ifneq (${PLAT},none)
|
|
TF_PLATFORM_ROOT := ../../plat/
|
|
include ${MAKE_HELPERS_DIRECTORY}plat_helpers.mk
|
|
PLAT_CERT_CREATE_HELPER_MK := ${PLAT_DIR}/cert_create_tbbr.mk
|
|
endif
|
|
|
|
# Common source files.
|
|
OBJECTS := src/cert.o \
|
|
src/cmd_opt.o \
|
|
src/ext.o \
|
|
src/key.o \
|
|
src/main.o \
|
|
src/sha.o
|
|
|
|
# Chain of trust.
|
|
ifeq (${COT},tbbr)
|
|
include src/tbbr/tbbr.mk
|
|
else ifeq (${COT},dualroot)
|
|
include src/dualroot/cot.mk
|
|
else ifeq (${COT},cca)
|
|
include src/cca/cot.mk
|
|
else
|
|
$(error Unknown chain of trust ${COT})
|
|
endif
|
|
|
|
ifneq (,$(wildcard ${PLAT_CERT_CREATE_HELPER_MK}))
|
|
include ${PLAT_CERT_CREATE_HELPER_MK}
|
|
endif
|
|
|
|
# Select OpenSSL version flag according to the OpenSSL build selected
|
|
# from setting the OPENSSL_DIR path.
|
|
$(eval $(call SELECT_OPENSSL_API_VERSION))
|
|
|
|
HOSTCCFLAGS := -Wall -std=c99
|
|
|
|
ifeq (${DEBUG},1)
|
|
HOSTCCFLAGS += -g -O0 -DDEBUG -DLOG_LEVEL=40
|
|
else
|
|
HOSTCCFLAGS += -O2 -DLOG_LEVEL=20
|
|
endif
|
|
|
|
ifeq (${V},0)
|
|
Q := @
|
|
else
|
|
Q :=
|
|
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 ${PLAT_INCLUDE} -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
|
|
|
|
HOSTCC ?= gcc
|
|
|
|
.PHONY: all clean realclean --openssl
|
|
|
|
all: --openssl ${BINARY}
|
|
|
|
${BINARY}: ${OBJECTS} Makefile
|
|
@echo " HOSTLD $@"
|
|
@echo 'const char build_msg[] = "Built : "__TIME__", "__DATE__; \
|
|
const char platform_msg[] = "${PLAT_MSG}";' | \
|
|
${HOSTCC} -c ${HOSTCCFLAGS} -xc - -o src/build_msg.o
|
|
${Q}${HOSTCC} src/build_msg.o ${OBJECTS} ${LIB_DIR} ${LIB} -o $@
|
|
|
|
%.o: %.c
|
|
@echo " HOSTCC $<"
|
|
${Q}${HOSTCC} -c ${HOSTCCFLAGS} ${INC_DIR} $< -o $@
|
|
|
|
--openssl:
|
|
ifeq ($(DEBUG),1)
|
|
@echo "Selected OpenSSL version: ${OPENSSL_CURRENT_VER}"
|
|
endif
|
|
|
|
clean:
|
|
$(call SHELL_DELETE_ALL, src/build_msg.o ${OBJECTS})
|
|
|
|
realclean: clean
|
|
$(call SHELL_DELETE,${BINARY})
|