summaryrefslogtreecommitdiffstats
path: root/support/docker
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2017-07-09 05:21:56 -0700
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2017-07-09 15:41:51 +0200
commitb3b60706221d75f3a0fce2441ce7a968981e7363 (patch)
tree365ac9f1b4a2ab4262ba7116d5fb59228afe52c8 /support/docker
parent15a96d1aaad32434bd63918ebdc09dd6468c630f (diff)
downloadbuildroot-b3b60706221d75f3a0fce2441ce7a968981e7363.tar.gz
buildroot-b3b60706221d75f3a0fce2441ce7a968981e7363.zip
arch/xtensa: allow specifying path to tarball file
currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'support/docker')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud