|
|
|
|
# Using ARM compilers from Linux command line is tricky and
|
|
|
|
|
# not really well documented because they want you to use
|
|
|
|
|
# their IDE instead.
|
|
|
|
|
#
|
|
|
|
|
# First you need to do the full install with the IDE and set
|
|
|
|
|
# up license files et al. This may be possible from the command
|
|
|
|
|
# line.
|
|
|
|
|
#
|
|
|
|
|
# Then you need to do the following:
|
|
|
|
|
#
|
|
|
|
|
# Select toolchain by running /opt/arm/developmentstudio-2019.0/bin/select_default_toolchain
|
|
|
|
|
# Armcc is only available in toolchain version 5.
|
|
|
|
|
# Armclang is only available in toolchain version 6.
|
|
|
|
|
# Start shell with /opt/arm/developmentstudio-2019.0/bin/suite_exec zsh
|
|
|
|
|
# Now the compilers will work.
|
|
|
|
|
|
|
|
|
|
[binaries]
|
|
|
|
|
# we could set exe_wrapper = qemu-arm-static but to test the case
|
|
|
|
|
# when cross compiled binaries can't be run we don't do that
|
|
|
|
|
c = ['/opt/arm/developmentstudio-2019.0/sw/ARMCompiler6.12/bin/armclang', '--target=aarch64-arm-none-eabi']
|
|
|
|
|
#c = '/opt/arm/developmentstudio-2019.0/sw/ARMCompiler5.06u6/bin/armcc'
|
|
|
|
|
#cpp = '/usr/bin/arm-linux-gnueabihf-g++'
|
|
|
|
|
ar = '/opt/arm/developmentstudio-2019.0/sw/ARMCompiler6.12/bin/armar'
|
|
|
|
|
#strip = '/usr/arm-linux-gnueabihf/bin/strip'
|
treewide: internally avoid deprecated machine file uses of "pkgconfig"
We support this in a machine file:
```
[binaries]
pkgconfig = 'pkg-config'
pkg-config = 'pkg-config'
```
and you can use either one, because internally we look up both. If you
only set *one* of them, this plays awkwardly with setting $PKG_CONFIG,
since we don't know which one you set in the machine file and the
*other* one will be initialized from the environment instead.
In commit 22df45a31981874310a78dde0df59a6a7c5ebb29 we changed program
lookup of config-tool style dependencies to use the regular tool names
and only fall back on the strange internal names. This affected the
pkg-config class too.
The result is that instead of preferring `pkgconfig =` followed by
$PKG_CONFIG followed by `pkg-config =`, we inverted the lookup order.
This is a good idea anyway, because now it behaves consistently with
`find_program('pkg-config')`.
Unfortunately, we documented the wrong name in a bunch of places, and
also used the wrong name in various testsuite bits, which meant that if
you set $PKG_CONFIG and then ran the testsuite, it would fail.
Correct these references, because they are buggy.
One test case expected to find_program() a native copy for convenience
of testing against natively installed glib. Force it to resolve a native
copy.
1 year ago
|
|
|
#pkg-config = '/usr/bin/arm-linux-gnueabihf-pkg-config'
|
|
|
|
|
|
|
|
|
|
[host_machine]
|
|
|
|
|
system = 'baremetal'
|
|
|
|
|
cpu_family = 'arm'
|
|
|
|
|
cpu = 'armv7' # Not sure if correct.
|
|
|
|
|
endian = 'little'
|
