Move app/service code from tactility-core to tactility (#14)
* Move app/service code from tactility-core to tactility * fix formatting * updated dev docs
This commit is contained in:
committed by
GitHub
parent
0c724e2e68
commit
e2209ccba8
@@ -56,10 +56,17 @@ The build scripts will detect if ESP-IDF is available. They will adapter if you
|
||||
|
||||
### Development
|
||||
|
||||
Directories explained:
|
||||
|
||||
- `app-esp`: The ESP32 application example
|
||||
- `app-sim`: The PC/simulator application example
|
||||
- `boards`: Contains ESP modules with drivers
|
||||
- `tactility`: The main application platform code ([src/](./tactility/src))
|
||||
- `tactility-esp`: ESP-specific application code (e.g. wifi app and service)
|
||||
- `tactility-core`: Core functionality regarding threads, stdlib, etc. ([src/](./tactility-core/src))
|
||||
- `libs`: Contains a mix of regular libraries and ESP modules
|
||||
|
||||
Until there is proper documentation, here are some pointers:
|
||||
- Sample application: [bootstrap](app-esp/src/main.c) and [app](app-esp/src/hello_world/hello_world.c)
|
||||
- [Tactility](./components/tactility): The main platform with default services and apps.
|
||||
- [Tactility Core](./tactility-core): The core platform code.
|
||||
|
||||
## License
|
||||
|
||||
|
||||
Reference in New Issue
Block a user