407b49b35c
Using find_package to locate Zephyr.
Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate
code.
Whenever an automatic run of CMake happend by the build system / IDE
then it was required that ZEPHYR_BASE was defined.
Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to
cache the base variable and thus allowing subsequent invocation even
if ZEPHYR_BASE is not set in the environment.
It also removes the risk of strange build results if a user switchs
between different Zephyr based project folders and forgetting to reset
ZEPHYR_BASE before running ninja / make.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
|
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.rst | ||
| prj.conf | ||
| sample.yaml | ||
README.rst
.. _net-promiscuous-mode-sample: Promiscuous Mode Sample Application ################################### Overview ******** This application will enable promiscuous mode for every network interface in the system. It will then start to listen for incoming network packets and show information about them. The application will also provide a shell so that user can enable or disable promiscuous mode at runtime. The commands are called ``promisc on`` and ``promisc off``. Requirements ************ - :ref:`networking_with_host` Building and Running ******************** There are multiple ways to use this application. In this example QEMU is used: .. zephyr-app-commands:: :zephyr-app: samples/net/promiscuous_mode :board: qemu_x86 :conf: <config file to use> :goals: build :compact: