Skip to content
Permalink
Browse files

getting_started: changes for custom toolchains

This option uses a lot of typing, so point out there's a way to save
keystrokes using -C.

Tweak the language around the target toolchain.

Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
  • Loading branch information...
mbolivar authored and nashif committed Jun 6, 2019
1 parent a506baf commit c98acc2a9a908948224846551909cad05e54ba0c
Showing with 12 additions and 4 deletions.
  1. +12 −4 doc/getting_started/toolchain_custom_cmake.rst
@@ -14,10 +14,10 @@ Zephyr will then include the toolchain cmake files located in the
:file:`TOOLCHAIN_ROOT` directory:

- :file:`cmake/toolchain/generic.cmake`: configures the toolchain for "generic"
use (mostly to run the C preprocessor on the generated :ref:`device-tree`
file).
- :file:`cmake/toolchain/target.cmake`: configures the toolchain for use
building Zephyr and your application's source code.
use, which mostly means running the C preprocessor on the generated
:ref:`device-tree` file.
- :file:`cmake/toolchain/target.cmake`: configures the toolchain for "target"
use, i.e. building Zephyr and your application's source code.

See the zephyr files :zephyr_file:`cmake/generic_toolchain.cmake` and
:zephyr_file:`cmake/target_toolchain.cmake` for more details on what your
@@ -29,3 +29,11 @@ variables when generating a build system for a Zephyr application, like so:
.. code-block:: console

cmake -DZEPHYR_TOOLCHAIN_VARIANT=... -DTOOLCHAIN_ROOT=...

If you do this, ``-C <initial-cache>`` `cmake option`_ may useful. If you save
your :makevar:`ZEPHYR_TOOLCHAIN_VARIANT`, :makevar:`TOOLCHAIN_ROOT`, and other
settings in a file named :file:`my-toolchain.cmake`, you can then invoke cmake
as ``cmake -C my-toolchain.cmake ...`` to save typing.

.. _cmake option:
https://cmake.org/cmake/help/latest/manual/cmake.1.html#options

0 comments on commit c98acc2

Please sign in to comment.
You can’t perform that action at this time.