ESP32 Forum

Hello,

I am trying to do things right: user components and tests
I am running however into a few issue and I have questions.

First of all, as there is for 'apps', is there a template repo that could be cloned for components?

I realized a few things that may help other, please comment if I am mistaken:
- you should write your components inside $IDF_PATH/components, other path won´t work
- ensure you have in your - you compile from with or - then you can flash, select your test and run it

Here are the issues I ran into. For the following, let´s assume my components is called myComp and located in . The make commands are ran from => works (telling me I can now flash, ...)
=> works, tell me I can flash
=> works, tell me I can flash
=> works

After that I tried introducing a typo in my components´ code. => all happy
=> the error is still not caught
=> the error is still not caught

A typo in the tests is caught properly however.

Disclaimer: I admit my C knowledge being rusty (no pun intended)

That what you're most likely looking for is the environment variable EXTRA_COMPONENT_DIRS

I've never tested it with multiple external component directories, but at least it works for me reliable for external folder.

A folder referenced here behaves similar to the components directory in the environment variable IDF_PATH. The only difference is that EXTRA_COMPONENT_DIRS must contain the path to the components folder directly.

Extra info test execution is not optimal, because the unity is not part of the SDK components. To execute tests in your reusable components directory add unity to the components and create the main similar to
https://github.com/espressif/esp-idf/bl ... app_main.c

I've reported this months ago with some other problems in the build system with external component folder. Everything except the unity folder was changed afterwards.

Great, thanks for your answer.

This topic is rather critical because I realized that if you have a bad component in one of the components folders, it will screw up your whole toolchain.

Would you mind being more specific regarding:

add unity to the components

I hope you don´t suggest adding all the unity files in each new component.
Or do you mind that unity should be brought as component to the EXTRA_COMPONENT_DIRS as well?

Once I sort that out, I am putting on Github a component template with the info I gathered, including what you just mentioned:
https://github.com/chevdor/esp32-component-template


Thanks again for your time answering.

I have a project that contains all my own components structured in the following way.
There are other alternatives too, but that's the one that I am using right now.

The Github repository that you mentioned has no proper License which makes it unusable for everyone else and a few unnecessary things. I try to find some time this weekend to wrap up the whole topic plus options up and but it in a repository.

That would be awesome and thanks a lot for sharing.
When all works on my end and the license is the last issue, I am more than happy to fix that on my end.
Let me know if I can help as well.

See https://esp32.com/viewtopic.php?f=18&t=2448