buildman: Try to avoid hard-coded string parsing
The assumption that the compiler name will always end in gcc is incorrect for clang and apparently on BSD. Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
parent
5abab20dfb
commit
b53241230d
|
@ -30,7 +30,14 @@ class Toolchain:
|
||||||
"""
|
"""
|
||||||
self.gcc = fname
|
self.gcc = fname
|
||||||
self.path = os.path.dirname(fname)
|
self.path = os.path.dirname(fname)
|
||||||
self.cross = os.path.basename(fname)[:-3]
|
|
||||||
|
# Find the CROSS_COMPILE prefix to use for U-Boot. For example,
|
||||||
|
# 'arm-linux-gnueabihf-gcc' turns into 'arm-linux-gnueabihf-'.
|
||||||
|
basename = os.path.basename(fname)
|
||||||
|
pos = basename.rfind('-')
|
||||||
|
self.cross = basename[:pos + 1] if pos != -1 else ''
|
||||||
|
|
||||||
|
# The architecture is the first part of the name
|
||||||
pos = self.cross.find('-')
|
pos = self.cross.find('-')
|
||||||
self.arch = self.cross[:pos] if pos != -1 else 'sandbox'
|
self.arch = self.cross[:pos] if pos != -1 else 'sandbox'
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue