Historia

Deomid Ryabkov 9903ea1c11 Add --warn-undefined-variables to MAKEFLAGS Fix warnings where undefined vars are used. Make Kconfig emit "FOO=" for unset bool options To ensure make variables are always defined, even if empty. When writing auto.conf, include symbols disabled by dependency to make sure all make variables are always defined. Fixes espressif/esp-idf#137 Cherry-picked from https://github.com/espressif/esp-idf/pull/138		2017-09-05 16:10:46 +10:00
..
bluetooth	Component/bt: add set local MTU API	2017-09-01 21:55:28 +08:00
ethernet	ethernet: remove CONFIG_ETHERNET	2017-08-18 08:31:43 +05:30
get-started	sdkconfig: Remove rest of the references to WIFI_ENABLED	2017-08-16 15:55:42 +05:30
performance	example: optimize the robust of TCP connect	2017-08-10 18:19:50 +08:00
peripherals	bugfix(timer group): remove floating-point in timer isr in example.	2017-08-30 23:30:53 +08:00
protocols	Add --warn-undefined-variables to MAKEFLAGS	2017-09-05 16:10:46 +10:00
storage	Merge branch 'feature/sdspi_driver' into 'master'	2017-07-26 13:51:37 +08:00
system	sleep: add light sleep, factor out APIs common for deep/light sleep	2017-09-01 10:36:14 +08:00
wifi	Add the fast crypto function in supplicant	2017-08-09 21:36:13 +08:00
README.md	examples: Standardise naming of files, symbols, etc. in examples	2017-03-27 17:42:05 +11:00

README.md

Examples

This directory contains a growing number of simple example projects for esp-idf. These are intended to show basic esp-idf functionality, and to provide you can use for your own projects.

Using Examples

Building examples is the same as building any other project:

Follow the setup instructions in the top-level esp-idf README.
Set IDF_PATH environment variable to point to the path to the esp-idf top-level directory.
Change into the directory of the example you'd like to build.
make menuconfig to configure the example. Most examples require a simple WiFi SSID & password via this configuration.
make to build the example.
Follow the printed instructions to flash, or run make flash.

Copying Examples

Each example is a standalone project. The examples do not have to be inside the esp-idf directory. You can copy an example directory to anywhere on your computer in order to make a copy that you can modify and work with.

The IDF_PATH environment variable is the only thing that connects the example to the rest of the esp-idf system.

If you're looking for a more bare-bones project to start from, try esp-idf-template.

Contributing Examples

If you have a new example you think we'd like, please consider sending it to us as a Pull Request.

Please read the esp-idf CONTRIBUTING.rst file which lays out general contribution rules.

In addition, here are some tips for creating good examples:

A good example is documented and the basic options can be configured.
A good example does not contain a lot of code. If there is a lot of generic code in the example, consider refactoring that code into a standalone component and then use the component's API in your example.
Names (of files, functions, variables, etc.) inside examples should be distinguishable from names of other parts of IDF (ideally, use example in names.)
Functions and variables used inside examples should be declared static where possible.
Examples should demonstrate one distinct thing each. Avoid multi-purposed "demo" examples, split these into multiple examples instead.
Examples must be licensed under the Apache License 2.0 or (preferably for examples) if possible you can declare the example to be Public Domain / Creative Commons Zero.