toolchain-external-custom: allow specifying relative path to binaries
authorCalin Crisan <ccrisan@gmail.com>
Sun, 25 Mar 2018 10:18:55 +0000 (13:18 +0300)
committerThomas Petazzoni <thomas.petazzoni@bootlin.com>
Thu, 19 Apr 2018 21:04:44 +0000 (23:04 +0200)
commit928c9289d25c47167c7e895f1a5f487067539b2c
tree29e85461de5a4fc84af9e1f44eb335a0b7fa8e9f
parente93fec6673eee4106a824cd357b2853cf8908a03
toolchain-external-custom: allow specifying relative path to binaries

There are cases where a downloaded toolchain doesn't have its binaries
placed directly in a "bin" subfolder (where BuildRoot currently looks
for them).

A common example is the official Raspberry Pi Toolchain
(https://github.com/raspberrypi/tools), which has its binaries in
"arm-bcm2708/arm-linux-gnueabihf/bin".

This commit introduces BR2_TOOLCHAIN_EXTERNAL_REL_BIN_PATH that defaults
to "bin" and can be changed as needed.

Signed-off-by: Calin Crisan <ccrisan@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
[Thomas: rework a bit how TOOLCHAIN_EXTERNAL_REL_BIN_PATH is defined.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
toolchain/toolchain-external/pkg-toolchain-external.mk
toolchain/toolchain-external/toolchain-external-custom/Config.in.options