Hello Manuel,
For my development, I chose the second option of the three that you provided.
During the development of the application project, I made a local library for it with the intent
to use it later on for other application projects. The first application project now compiles and runs.
For the development of the second application (using a different board, by the way),
I created a lib directory in the directory that contains the two application projects,
and moved the library there. In the first application project, I updated lib_extra_dirs accordingly,
and my first application now compiles again. So far so good!
Now in order to make the library work also for the second application project,
I would like to open the files in the library and edit them, without compiling of course.
Compiling (and linking) will be done in the two application projects (for different boards).
Now I can open them by using “open file” in the top left corner,
and then I need to browse through my directory structure to find it.
That works, but it is somewhat cumbersome. Is there perhaps any way to create
something that I would call a library project, so that it can be added to my workspace?
That would allow the files to be opened just like the application project files.
I did put in some effort to find information on this topic, but unsuccessfully so.
The closest I could find is
but this talks only about the file structure, and assumes the library is external.
My question is about a home-brew library in more or less the same file structure.
Many thanks in advance!