michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: application: Remove accidental backslashes in Kconfig sample

Browse source 
The SOC Definitions section had backslashes before * in globbing
'source's.

Also change the language for the code block from 'console' to 'none'.
Kconfig isn't shell.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
This commit is contained in:
Ulf Magnusson 2019-12-04 12:29:07 +01:00 • committed by Carles Cufí
commit acc829c3ee
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/application/index.rst
View file

@ -675,7 +675,7 @@ SOC Definitions
Similar to board support, the structure is similar to how SOCs are maintained in Similar to board support, the structure is similar to how SOCs are maintained in
the Zephyr tree, for example: the Zephyr tree, for example:
.. code-block:: console .. code-block:: none
soc soc
└── arm └── arm
@ -693,19 +693,19 @@ In the ``soc`` directory you will need a top-level Kconfig file pointing to the
custom SOC definitions: custom SOC definitions:
.. code-block:: console .. code-block:: none
choice choice
prompt "SoC/CPU/Configuration Selection" prompt "SoC/CPU/Configuration selection"
source "$(SOC_DIR)/$(ARCH)/\*/Kconfig.soc" source "$(SOC_DIR)/$(ARCH)/*/Kconfig.soc"
endchoice endchoice
menu "Hardware Configuration" menu "Hardware Configuration"
osource "$(SOC_DIR)/$(ARCH)/\*/Kconfig" osource "$(SOC_DIR)/$(ARCH)/*/Kconfig"
endmenu endmenu
Once the SOC structure is in place, you can build your application Once the SOC structure is in place, you can build your application
targeting this platform by specifying the location of your custom platform targeting this platform by specifying the location of your custom platform