Calin Crisan 928c9289d2 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>		2018-04-19 23:04:44 +02:00
..
toolchain
toolchain-buildroot	toolchain, gcc, gdb, binutils, uclibc: remove Blackfin code	2018-04-15 22:05:14 +02:00
toolchain-external	toolchain-external-custom: allow specifying relative path to binaries	2018-04-19 23:04:44 +02:00
Config.in	toolchain, gcc, gdb, binutils, uclibc: remove Blackfin code	2018-04-15 22:05:14 +02:00
helpers.mk
toolchain-wrapper.c	toolchain-wrapper: use -ffp-contract=off on MIPS Xburst for gcc >= 4.6	2018-04-01 16:23:33 +02:00
toolchain-wrapper.mk	toolchain-wrapper: use -ffp-contract=off on MIPS Xburst for gcc >= 4.6	2018-04-01 16:23:33 +02:00
toolchain.mk	toolchain/toolchain.mk: fix code style	2018-04-01 08:47:18 +02:00