mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-06-25 13:41:36 +00:00
Kaj Schittecat
1f6409702c
First board lands. wadamesh builds the LVGL touch firmware as its own project, consuming the MeshCore core via lib_deps @ git tag (ALLFATHER-BV/MeshCore #v1.16.0-wada.0) — no vendored core in this repo. Output is byte-identical to the in-tree meshcomod build (delta = embedded build-path strings only). Contents: companion_radio app (MyMesh/main/DataStore), ui-touch LVGL UI, variants/heltec_v4 board glue, boards/heltec_v4.json, lv_conf, the bundled ed25519 lib, AsyncElegantOTA, partition table, and a flattened platformio.ini for env heltec_v4_tft_companion_radio_usb_tcp_touch. MeshCore-derived files (app glue) remain MIT; ui-touch is GPL — see NOTICE. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Kaj Schittecat <kaj@schittecat.com>
40 lines
1.4 KiB
Plaintext
40 lines
1.4 KiB
Plaintext
|
|
This directory is intended for project header files.
|
|
|
|
A header file is a file containing C declarations and macro definitions
|
|
to be shared between several project source files. You request the use of a
|
|
header file in your project source file (C, C++, etc) located in `src` folder
|
|
by including it, with the C preprocessing directive `#include'.
|
|
|
|
```src/main.c
|
|
|
|
#include "header.h"
|
|
|
|
int main (void)
|
|
{
|
|
...
|
|
}
|
|
```
|
|
|
|
Including a header file produces the same results as copying the header file
|
|
into each source file that needs it. Such copying would be time-consuming
|
|
and error-prone. With a header file, the related declarations appear
|
|
in only one place. If they need to be changed, they can be changed in one
|
|
place, and programs that include the header file will automatically use the
|
|
new version when next recompiled. The header file eliminates the labor of
|
|
finding and changing all the copies as well as the risk that a failure to
|
|
find one copy will result in inconsistencies within a program.
|
|
|
|
In C, the usual convention is to give header files names that end with `.h'.
|
|
It is most portable to use only letters, digits, dashes, and underscores in
|
|
header file names, and at most one dot.
|
|
|
|
Read more about using header files in official GCC documentation:
|
|
|
|
* Include Syntax
|
|
* Include Operation
|
|
* Once-Only Headers
|
|
* Computed Includes
|
|
|
|
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html
|