ESP_Angus wrote:kolban wrote:Might we as a community not choose to back/support/utilize an existing framework such as this one?
This is more or less our long term plan, to have a package management system of some kind. It will need to be IDF-specific in some ways, but we want to leverage existing tools as much as possible.
The plan is to do this in stages: start with a simple list, and work towards a list where the third party components are easy to drop into a project components directory (ie have a component.mk file, config, etc). Then use what we learn from that process to inform the final design of a package manager that automates the step of downloading a new component into a project.
Angus
thats sound is great Angus.
CAN compo comes exactly like you desribed as third party next days - i wait only for thomas come back from be away - he is on the road
ESPCAN Driver package
components/ESPCAN
components/ESPCAN -> readme
components/ESPCAN -> component.mk
components/ESPCAN -> can.c
components/ESPCAN -> kconfig
components/ESPCAN/include
components/ESPCAN/include -> can.h
components/ESPCAN/include -> can_config.h
components/ESPCAN/include -> can_regdef.h
ESPCAN Demo package
examples/ESPCAN/nodeunit
examples/ESPCAN/nodeunit-> Makefile
examples/ESPCAN/nodeunit/unit
examples/ESPCAN/nodeunit/unit -> unit.c
examples/ESPCAN/nodeunit/unit -> component.mk
examples/ESPCAN/controllunit
examples/ESPCAN/controllunit -> Makefile
examples/ESPCAN/controllunit/cunit
examples/ESPCAN/controllunit/cunit -> cunit.c
examples/ESPCAN/controllunit/cunit -> component.mk
and yes, description for wiring, pic and so on too.
btw:
work same component principal in our opensource
ESP32 IDE for teach
and yes - its fully ESP-IDF guidline strategie and compatible. its a flowcharter IDE thats generate the code from flowcharts..
but this is an other theme
best wishes
rudi