You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> set ARMLMD_LICENSE_FILE=c:\<path>\license_armds.dat
92
+
# Windows, license server:
93
+
> set ARMLMD_LICENSE_FILE=8224@myserver
94
+
95
+
#. If the Arm Compiler 6 was installed as part of an Arm Development Studio, then
96
+
you must set the :envvar:`ARM_PRODUCT_DEF` to point to the product definition file:
97
+
See also: `Product and toolkit configuration <https://developer.arm.com/tools-and-software/software-development-tools/license-management/resources/product-and-toolkit-configuration>`_.
98
+
For example if the Arm Development Studio is installed in:
99
+
``/opt/armds-2020-1`` with a Gold license, then set :envvar:`ARM_PRODUCT_DEF`
100
+
to point to ``/opt/armds-2020-1/gold.elmap``.
101
+
102
+
.. note::
103
+
104
+
The Arm Compiler 6 uses ``armlink`` for linking. This is incompatible
105
+
with Zephyr's linker script template, which works with GNU ld. Zephyr's
106
+
Arm Compiler 6 support Zephyr's CMake linker script generator, which
107
+
supports generating scatter files. Basic scatter file support is in
108
+
place, but there are still areas covered in ld templates which are not
109
+
fully supported by the CMake linker script generator.
110
+
111
+
Some Zephyr subsystems or modules may also contain C or assembly code
112
+
that relies on GNU intrinsics and have not yet been updated to work fully
113
+
with ``armclang``.
114
+
64
115
Intel oneAPI Toolkit
65
116
*********************
66
117
@@ -161,3 +212,4 @@ You can build toolchains from source code using crosstool-NG.
161
212
162
213
.. _GNU ARM Embedded: https://developer.arm.com/open-source/gnu-toolchain/gnu-rm
0 commit comments