mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 13:32:33 +00:00
2975ca0754
The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Makefile | ||
| prj_single.conf | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _hello_world:
Hello World
###########
Overview
********
A simple Hello World example that can be used with any supported board and
prints 'Hello World' to the console. This application can be built into modes:
* single thread
* multi threading
Building and Running
********************
This project outputs 'Hello World' to the console. It can be built and executed
on QEMU as follows:
.. code-block:: console
$ cd samples/hello_world
$ make run
To build the single thread version, use the supplied configuration file for
single thread: :file:`prj_single.conf`:
.. code-block:: console
$ make CONF_FILE=prj_single.conf run
Sample Output
=============
.. code-block:: console
Hello World! x86