mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-17 18:14:24 +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>
63 lines
1.4 KiB
Makefile
63 lines
1.4 KiB
Makefile
#
|
|
# Copyright (c) 2016-2018, ARM Limited and Contributors. All rights reserved.
|
|
#
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
|
#
|
|
|
|
# Trusted Firmware shell command definitions for a Unix style environment.
|
|
|
|
ifndef UNIX_MK
|
|
UNIX_MK := $(lastword $(MAKEFILE_LIST))
|
|
|
|
ECHO_BLANK_LINE := echo
|
|
ECHO_QUIET := @\#
|
|
|
|
DIR_DELIM := /
|
|
PATH_SEP := :
|
|
|
|
# These defines provide Unix style equivalents of the shell commands
|
|
# required by the Trusted Firmware build environment.
|
|
|
|
# ${1} is the file to be copied.
|
|
# ${2} is the destination file name.
|
|
define SHELL_COPY
|
|
${Q}cp -f "${1}" "${2}"
|
|
endef
|
|
|
|
# ${1} is the directory to be copied.
|
|
# ${2} is the destination directory path.
|
|
define SHELL_COPY_TREE
|
|
${Q}cp -rf "${1}" "${2}"
|
|
endef
|
|
|
|
# ${1} is the file to be deleted.
|
|
define SHELL_DELETE
|
|
-${Q}rm -f "${1}"
|
|
endef
|
|
|
|
# ${1} is a space delimited list of files to be deleted.
|
|
# Note that we do not quote ${1}, as multiple parameters may be passed.
|
|
define SHELL_DELETE_ALL
|
|
-${Q}rm -rf ${1}
|
|
endef
|
|
|
|
# ${1} is the directory to be generated.
|
|
# ${2} is optional, and allows a prerequisite to be specified.
|
|
# Do nothing if $1 == $2, to ignore self dependencies.
|
|
define MAKE_PREREQ_DIR
|
|
ifneq (${1},${2})
|
|
|
|
${1} : ${2}
|
|
${Q}mkdir -p "${1}"
|
|
|
|
endif
|
|
endef
|
|
|
|
define SHELL_REMOVE_DIR
|
|
-${Q}rm -rf "${1}"
|
|
endef
|
|
|
|
nul := /dev/null
|
|
|
|
which = $(shell which $(1) 2>$(nul))
|
|
endif
|