What's the deal with the PlatformIO linking & project folders?

I cannot seem to find a consistent way to utilize the “lib” and “include” folders. Some projects I can place files in them. Others won’t link. Some link when in “lib” folder, some in “include” folder, and some only when code is in the “src” folder. I’ve fiddled with this days trying to figure this out along with searching the internet. Maybe I’m just dense so giving up and asking here what’s up with this.

I’ve latest versions in my toolchain (ESP32 xtensa compiler). A good concise breakdown of how the folders will behave consistently would be greatly appreciated. Maybe it’s the underlying compiler that’s causing me grief?

Preferably I’d be able to use both lib and include folders as they do help keep large projects organized.

On this particular project if I move the code containing flagged references to source folder it will link. Otherwise, the compiler does the following:

The include paths are inside the .vscode json file as expected

I have latest toolkit / compiler.

Everything is explained in the README files inside the directories:

include/README:

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’.


#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 convention is to give header files names that end with `.h’.

Read more about using header files in official GCC documentation:

  • Include Syntax
  • Include Operation
  • Once-Only Headers
  • Computed Includes

Header Files (The C Preprocessor)

Note: This is about project header files. So instad having your projects header files in the src directory, you can place them into the include directory.

.
├── include
│   ├── file1.h
│   ├── file2.h
│   ├── file3.h
├── lib
├── src
│   ├── file1.cpp
│   ├── file2.cpp
│   └── file3.cpp
├── test
└── platformio.ini

lib/README:

This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into the executable file.

The source code of each library should be placed in a separate directory
(“lib/your_library_name/[Code]”).

For example, see the structure of the following example libraries Foo and Bar:

.
├── lib
│   ├── Bar
│   │   ├── doc
│   │   ├── examples
│   │   ├── src
│   │   │   ├── Bar.cpp
│   │   │   └── Bar.h
│   │   └── library.json (optional. for custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
│   ├── Foo
│   │   ├── Foo.c
│   │   └── Foo.h
│   └── README --> THIS FILE
├── platformio.ini
├── src
│   └── main.c

Example contents of src/main.c using Foo and Bar:

#include <Foo.h>
#include <Bar.h>

int main (void)
{
  ...
}

The PlatformIO Library Dependency Finder will find automatically dependent
libraries by scanning project source files.

More information about PlatformIO Library Dependency Finder

2 Likes

Thanks for pointing the readme files. I have read them. The software is not behaving as described in the readme though.

I have some projects which will find the header files in the include folder others which will not. I cannot figure out why. Is it a bug in PlatformIO or the compiler or what? The compiler crashes upon linking. It cannot find the build files for files within the lib and or include folders. I cannot seem to get it to behave consistently from project to project to figure out what’s aggravating this issue.

As for the lib folder I have had virtually no luck getting that to work as in the readme file. It seldom finds anything in there. It’s worked on maybe one project… I don’t keep a good log of when things behave weirdly (which I know doesn’t help debug this stuff). I notice that folder isn’t included in the path declarations in the json file though… so maybe that’s why I cannot use the lib folder?

I think this may actually be a bug in the software… be it in PlatformIO and or the xtensa compiler? Idk?

Anybody from Platform IO development team able to chip in?

But it does.
Please let us know the reasons how you came to your conclusion.

This isn’t done by PlatformIO but by the programme who wrote the project. So it’s up to you / the programmer to use the directories correctly.

Please show the project so we have something we can discuss about.

Again, it is up to the programmer to use the directories.

Please show the project

It works on every project (if it is done correctly)
Again, we need a concrete project here

I don’t think so

Maybe this project helps you to understand how the directories are used correctly: