• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

CMakeLists.txtD11-Mar-2024848 2822

README.mdD11-Mar-20241.5 KiB2615

esp_local_ctrl.protoD11-Mar-20241.3 KiB6351

makefileD11-Mar-2024209 85

README.md

1# Protobuf files for defining ESP Local Control message structures
2
3The proto files under this directory are used by esp_local_ctrl for defining protobuf messages which are sent and received over protocomm transport layer. These proto files cannot be used directly and have to be compiled into C and Python files. The generated C files are used by esp_local_ctrl itself to create, delete and manipulate transaction packets. The generated Python files can be used by python based applications for implementing client side interface to esp_local_ctrl service running on a device.
4
5Note : These proto files are not automatically compiled during the build process.
6
7# Compilation
8
9Compilation requires protoc (Protobuf Compiler) and protoc-c (Protobuf C Compiler) installed. Since the generated files are to remain the same, as long as the proto files are not modified, therefore the generated files are already available under `components/esp_local_ctrl/proto-c` and `components/esp_local_ctrl/python` directories, and thus running `cmake` / `make` (and installing the Protobuf compilers) is optional.
10
11If using `cmake` follow the below steps. If using `make`, jump to Step 2 directly.
12
13## Step 1 (Only for cmake)
14
15When using cmake, first create a build directory and call cmake from inside:
16
17```
18mkdir build
19cd build
20cmake ..
21```
22
23## Step 2
24
25Simply run `make` to generate the respective C and Python files. The newly created files will overwrite those under `components/esp_local_ctrl/proto-c` and `components/esp_local_ctrl/python`
26