3
3
Template repository for building an ESP app with ESP++ (espp) components and
4
4
ESP-IDF components.
5
5
6
+ <!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-refresh-toc -->
7
+ ** Table of Contents**
8
+
9
+ - [ ESP++ Template] ( #esp-template )
10
+ - [ Development] ( #development )
11
+ - [ Build and Flash] ( #build-and-flash )
12
+ - [ Output] ( #output )
13
+ - [ Developing] ( #developing )
14
+ - [ Code style] ( #code-style )
15
+
16
+ <!-- markdown-toc end -->
17
+
6
18
## Development
7
19
8
20
This repository is designed to be used as a template repository - so you can
9
21
sepcify this as the template repository type when creating a new repository on
10
22
GitHub.
11
23
12
24
After setting this as the template, make sure to update the following:
13
- - [ This README] ( ./README.md ) to contain the relevant description and images of your project
14
- - The [ ./CMakeLists.txt] ( ./CMakeLists.txt ) file to have the components that you
15
- want to use (and any you may have added to the [ components
16
- folder] ( ./components ) ) as well as to update the project name
25
+ - [ This README] ( ./README.md ) to contain the relevant description and images of
26
+ your project
27
+ - Add additional component dependencies you may want, e.g.:
28
+
29
+ ``` console
30
+ idf.py add-dependency "espp/timer^0.21.0"
31
+ ```
32
+
33
+ - The [./CMakeLists.txt](./CMakeLists.txt) file to update the project name.
17
34
- The [./main/main.cpp](./main/main.cpp) To run the main code for your app. The
18
35
[main folder](./main) is also where you can put additional header and source
19
36
files that you don't think belong in their own components but help keep the
@@ -27,22 +44,6 @@ After setting this as the template, make sure to update the following:
27
44
analysis tool to put its results into a comment on any pull requests in your
28
45
repository.
29
46
30
- ## Cloning
31
-
32
- Since this repo contains a submodule, you need to make sure you clone it
33
- recursively, e.g. with:
34
-
35
- ``` sh
36
- git clone --recurse-submodules < your repo name>
37
- ```
38
-
39
- Alternatively, you can always ensure the submodules are up to date after cloning
40
- (or if you forgot to clone recursively) by running:
41
-
42
- ``` sh
43
- git submodule update --init --recursive
44
- ```
45
-
46
47
## Build and Flash
47
48
48
49
Build the project and flash it to the board, then run monitor tool to view serial output:
0 commit comments