zephyr/doc/getting_started/toolchain_host.rst

.. _host_toolchains:

Host Toolchains
###############

In some specific configurations, like when building for non-MCU x86 targets on
a Linux host, you may be able to re-use the native development tools provided
by your operating system.

To use your host gcc, set the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT`
:ref:`environment variable <env_vars>` to ``host``. To use clang, set
:envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``llvm``.
doc: periodic updates to getting started guide Updates based on discussion and changes in supported features. - Make the guide shorter by removing content that's not relevant to most users who are truly just getting started, such as information about pre-LTS versions that did not support west, and by being more concise in some places. - Decrease the number of colored boxes. At the latest TSC F2F, the "note / warning / note / tip" contents were identified as a readability problem. - Add additional information based on new west features, like "west boards". Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no> 2019-05-13 22:07:57 +02:00			`.. _host_toolchains:`

			`Host Toolchains`
			`###############`

			`In some specific configurations, like when building for non-MCU x86 targets on`
			`a Linux host, you may be able to re-use the native development tools provided`
			`by your operating system.`

			To use your host gcc, set the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT`
			:ref:`environment variable <env_vars>` to ``host``. To use clang, set
doc: getting_started: Fix clang toolchain use In order to use clang it is necessary to set the variable ZEPHYR_TOOLCHAIN_VARIANT to llvm instead of clang. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com> 2019-11-12 00:36:58 +01:00			:envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``llvm``.