Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Ulf Magnusson 214ef00db3 kconfig: subsys: net: Remove redundant dependencies
subsys/net/lib/lwm2m/Kconfig.ipso is 'source'd within an 'if LWM2M', in
subsys/net/lib/lwm2m/Kconfig, so the 'depends on LWM2M' is redundant.

The 'depends on NET_IPV4' and 'depends on NET_L2_OPENTHREAD' are within
corresponding 'if's in the same file.

'if FOO' is just shorthand for adding 'depends on FOO' to each item
within the 'if'. Dependencies on menus work similarly. There are no
"conditional includes" in Kconfig, so 'if FOO' has no special meaning
around a source. Conditional includes wouldn't be possible, because an
if condition could include (directly or indirectly) forward references
to symbols not defined yet.

Tip: When adding a symbol, check its dependencies in the menuconfig
('ninja menuconfig', then / to jump to the symbol). The menuconfig also
shows how the file with the symbol got included, so if you see
duplicated dependencies, it's easy to hunt down where they come from.

Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-09 09:49:59 -05:00
.github/ISSUE_TEMPLATE templates: Update issue templates 2018-12-07 08:27:20 -05:00
.known-issues doc: introduce final structure 2019-02-05 07:04:40 -05:00
arch arch/x86_64: Non-kconfig symbols shouldn't look like kconfig 2019-03-08 06:53:39 -05:00
boards boards: arm: particle_*: remove SPI default enablement 2019-03-07 20:30:27 -05:00
cmake kconfig: Have ninja Re-run CMake when Kconfig sources change 2019-03-07 10:40:00 +01:00
doc scripts: Add hook calllable series-push-hook script 2019-03-08 16:43:06 -05:00
drivers kconfig: drivers: wifi: Remove redundant WIFI deps. 2019-03-09 09:49:26 -05:00
dts dts: usbserial: Fix USB serial console device name 2019-03-09 10:41:05 +01:00
ext soc: nxp_kinetis: Add HAS_MCUX_FTFX to conditionalize mcux flash driver 2019-03-06 21:19:25 -06:00
include kernel/work_q: Clarify docs for k_delayed_work_cancel() 2019-03-08 16:43:56 -05:00
kernel kernel: Make statements evaluate boolean expressions 2019-03-05 14:58:58 -08:00
lib kconfig: lvgl: Remove redundant LVGL dep. 2019-03-09 09:48:25 -05:00
misc cmake: Rename CMake variable out of the reserved CONFIG_ namespace 2019-03-03 23:52:29 -05:00
samples sample: sockets: can: Update error handle flow 2019-03-08 08:43:29 -05:00
scripts scripts: Add hook calllable series-push-hook script 2019-03-08 16:43:06 -05:00
soc soc: nxp_kinetis: Add HAS_MCUX_FTFX to conditionalize mcux flash driver 2019-03-06 21:19:25 -06:00
subsys kconfig: subsys: net: Remove redundant dependencies 2019-03-09 09:49:59 -05:00
tests net: tests: Migrate ARP tests 2019-03-08 07:18:19 -05:00
.checkpatch.conf
.clang-format
.codecov.yml
.editorconfig editorconfig: basic EditorConfig configuration 2019-02-07 08:15:23 -05:00
.gitattributes
.gitignore gitignore: ignore IDE files 2018-11-21 15:05:07 +01:00
.gitlint gitlint: do not start with subsys: 2018-11-28 09:22:01 -08:00
.mailmap
.shippable.yml ci: Use latest docker image: 0.6.1 2019-02-19 11:30:27 -05:00
.uncrustify.cfg
CMakeLists.txt mbedtls: provide user mode access 2019-03-05 08:27:20 -05:00
CODEOWNERS scripts: Add hook calllable series-push-hook script 2019-03-08 16:43:06 -05:00
CODE_OF_CONDUCT.md coc: move to markdown format 2019-01-24 15:37:15 -05:00
CONTRIBUTING.rst doc: Fixed a link in CONTRIBUTING.rst 2019-02-28 12:46:04 -08:00
Kconfig
Kconfig.zephyr lib/os: Conditionally eliminate alloca/VLA usage 2019-02-28 10:06:35 -08:00
LICENSE
Makefile doc: add clean target to Makefile 2019-02-05 16:58:14 -05:00
README.rst doc: Fix links to docs.zephyrproject.org 2019-02-18 17:18:33 -05:00
VERSION release: Zephyr 1.14-rc1 2019-02-11 11:12:14 -06:00
version.h.in
west.yml west: add west.yml 2019-01-29 10:15:01 +01:00
zephyr-env.cmd scripts: remove west from scripts/ 2019-01-29 10:15:01 +01:00
zephyr-env.sh shell: Piped output of cd to /dev/null when setting ZEPHYR_BASE. 2018-12-06 19:14:50 -05:00

README.rst

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

.. below included in doc/introduction/introduction.rst

.. start_include_here

Getting Started
***************

To start developing Zephyr applications refer to the `Getting Started Guide`_
in the `Zephyr Documentation`_ pages.
A brief introduction to Zephyr can be found in the  `Zephyr Introduction`_
page.

Community Support
*****************

The Zephyr Project Developer Community includes developers from member
organizations and the general community all joining in the development of
software within the Zephyr Project. Members contribute and discuss ideas,
submit bugs and bug fixes, and provide training. They also help those in need
through the community's forums such as mailing lists and IRC channels. Anyone
can join the developer community and the community is always willing to help
its members and the User Community to get the most out of the Zephyr Project.

Welcome to the Zephyr community!

Resources
*********

Here's a quick summary of resources to find your way around the Zephyr Project
support systems:

* **Zephyr Project Website**: The https://zephyrproject.org website is the
  central source of information about the Zephyr Project. On this site, you'll
  find background and current information about the project as well as all the
  relevant links to project material.

* **Releases**: Source code for Zephyr kernel releases are available at
  https://zephyrproject.org/developers/#downloads. On this page,
  you'll find release information, and links to download or clone source
  code from our GitHub repository.  You'll also find links for the Zephyr
  SDK, a moderated collection of tools and libraries used to develop your
  applications.

* **Source Code in GitHub**: Zephyr Project source code is maintained on a
  public GitHub repository at https://github.com/zephyrproject-rtos/zephyr.
  You'll find information about getting access to the repository and how to
  contribute to the project in this `Contribution Guide`_ document.

* **Samples Code**: In addition to the kernel source code, there are also
  many documented `Sample and Demo Code Examples`_ that can help show you
  how to use Zephyr services and subsystems.

* **Documentation**: Extensive Project technical documentation is developed
  along with the Zephyr kernel itself, and can be found at
  http://docs.zephyrproject.org.  Additional documentation is maintained in
  the `Zephyr GitHub wiki`_.

* **Cross-reference**: Source code cross-reference for the Zephyr
  kernel and samples code is available at
  https://elixir.bootlin.com/zephyr/latest/source.

* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
  the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues.
  You can browse through the reported issues and submit issues of your own.

* **Security-related Issue Reporting and Tracking**: For security-related
  inquiries or reporting suspected security-related bugs in the Zephyr OS,
  please send email to vulnerabilities@zephyrproject.org.  We will assess and
  fix flaws according to our security policy outlined in the Zephyr Project
  `Security Overview`_.

  Security related issue tracking is done in JIRA.  The location of this JIRA
  is https://zephyrprojectsec.atlassian.net.

* **Mailing List**: The `Zephyr Development mailing list`_ is perhaps the most convenient
  way to track developer discussions and to ask your own support questions to
  the Zephyr project community.  There are also specific `Zephyr mailing list
  subgroups`_ for announcements, builds, marketing, and Technical
  Steering Committee notes, for example.
  You can read through the message archives to follow
  past posts and discussions, a good thing to do to discover more about the
  Zephyr project.

* **Chatting**: You can chat online with the Zephyr project developer
  community and other users in two ways:

  * On `Slack`_: Zephyr has dedicated channels on Slack. To register, use the
    following `Slack Invite`_.

  * IRC channel #zephyrproject on the freenode.net IRC server. You can use the
    http://webchat.freenode.net web client or use a client-side application such
    as pidgin (Note that all discussions have moved to Slack, although we still
    have many developers still available on the IRC channel).

.. _Slack Invite: https://tinyurl.com/yarkuemx
.. _Slack: https://zephyrproject.slack.com
.. _supported boards: http://docs.zephyrproject.org/latest/boards
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Zephyr Introduction: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security Overview: http://docs.zephyrproject.org/latest/security/index.html