79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.rst | ||
| overlay-802154.conf | ||
| overlay-bt.conf | ||
| overlay-qemu_cortex_m3_eth.conf | ||
| prj.conf | ||
| sample.yaml | ||
README.rst
.. _mdns-responder-sample:
mDNS Responder Application
##########################
Overview
********
This application will wait mDNS queries for a pre-defined hostname and
respond to them. The default hostname is **zephyr** and it is set in the
:file:`prj.conf` file.
Requirements
************
- :ref:`networking_with_host`
- avahi or similar mDNS capable application that is able to query mDNS
information.
Building and Running
********************
Build and run the mdns-responder sample application like this:
.. zephyr-app-commands::
:zephyr-app: samples/net/mdns_responder
:board: <board to use>
:conf: <config file to use>
:goals: build
:compact:
After the mdns-responder sample application is started, it will await queries
from the network.
Open a terminal window in your host and type:
.. code-block:: console
$ avahi-resolve -4 -n zephyr.local
If the query is successful, then following information is printed:
.. code-block:: console
zephyr.local 192.0.2.1
For a IPv6 query, type this:
.. code-block:: console
$ avahi-resolve -6 -n zephyr.local
If the query is successful, then following information is printed:
.. code-block:: console
zephyr.local 2001:db8::1
Lastly, resolve services using DNS Service Discovery:
.. code-block:: console
$ avahi-browse -t -r _zephyr._tcp
If the query is successful, then the following information is printed:
.. code-block:: console
+ zeth IPv6 zephyr _zephyr._tcp local
= zeth IPv6 zephyr _zephyr._tcp local
hostname = [zephyr.local]
address = [192.0.2.1]
port = [4242]
txt = []