toolchain-external: move wrapper to toolchain directory
authorArnout Vandecappelle <arnout@mind.be>
Sun, 4 Oct 2015 12:28:41 +0000 (13:28 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Sun, 4 Oct 2015 16:22:19 +0000 (18:22 +0200)
commitf6ae24379b551cbfc6447b25a241ffa76d366ddc
tree16214940d57b612b6cd35d8859bff1cf2dac857a
parentad9c7ee554bb8b6f69429e8d1585d0555a42f06c
toolchain-external: move wrapper to toolchain directory

The toolchain wrapper will be reused for the internal toolchain, so it
belongs in the toolchain directory. Also, the ext- prefix is removed
from it. The build commands are moved to a new toolchain-wrapper.mk.

The wrapper arguments that are also relevant for the internal toolchain
wrapper are moved to toolchain-wrapper.mk, the rest stays in
toolchain-external.mk.

While we're at it, move the building of the toolchain wrapper to the
build step of toolchain-external. There is no specific reason to do
this, other than that it fits better semantically. Also remove the
MESSAGE call, otherwise we'd see:
>>> toolchain-external undefined Building
>>> toolchain-external undefined Building toolchain wrapper
/usr/bin/gcc ...
Having an extra "Building toolchain wrapper' message is pointless.

The useless condition on $(BR2_TARGET_OPTIMIZATION) is removed. It was
always true because it wasn't qstrip'ped first, so clearly it works
without that condition as well.

Also rewrapped some comments and removed the 'external' reference.

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: Fabio Porcedda <fabio.porcedda@gmail.com>
Cc: Jérôme Oufella <jerome.oufella@savoirfairelinux.com>
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
toolchain/toolchain-external/ext-toolchain-wrapper.c [deleted file]
toolchain/toolchain-external/toolchain-external.mk
toolchain/toolchain-wrapper.c [new file with mode: 0644]
toolchain/toolchain-wrapper.mk [new file with mode: 0644]