Skip to content

Commit

Permalink
doc: picolibc: a few words about building without native support
Browse files Browse the repository at this point in the history
This adds a few words about using Picolibc without native support
from toolchain, and how to enable this behavior for toolchain.

Signed-off-by: Daniel Leung <daniel.leung@intel.com>
  • Loading branch information
dcpleung authored and nashif committed Sep 13, 2023
1 parent b21d35d commit 26ffa9f
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions doc/develop/languages/c/picolibc.rst
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,28 @@ For every release of Zephyr, the toolchain-bundled Picolibc and the
sync when using the
:ref:`recommended version of Zephyr SDK <toolchain_zephyr_sdk_compatibility>`.

Building Without Toolchain bundled Picolibc
-------------------------------------------

For toolchain where there is no bundled Picolibc, it is still
possible to use Picolibc by building it from source. Note that
any restrictions mentioned in :ref:`c_library_picolibc_module`
still apply.

To build without toolchain bundled Picolibc, the toolchain must
enable :kconfig:option:`CONFIG_PICOLIBC_SUPPORTED`. For example,
this needs to be added to the toolchain Kconfig file:

.. code-block:: none
config TOOLCHAIN_<name>_PICOLIBC_SUPPORTED
def_bool y
select PICOLIBC_SUPPORTED
By enabling :kconfig:option:`CONFIG_PICOLIBC_SUPPORTED`, the build
system would automatically build Picolibc from source with its module
when there is no toolchain bundled Picolibc.

Formatted Output
****************

Expand Down

0 comments on commit 26ffa9f

Please sign in to comment.