We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Original issue raised here : https://community.platformio.org/t/lib-deps-include-paths-are-messed-up/13827
I added a library to platformio.ini : lib_deps = mbed-http
Great so it downloaded the dependency, with the structure:
(I think http_parser is a dependency of mbed-http)
However, if I want to include the library in my project, I need to use fully qualified paths :
#include <source/http_request.h> #include <http_parser/http_parser.h>
But I also need to go into the library and change the internal library dependencies, so in http_request.h:
#include "http_parser.h" // Doesn't work #include "http_parser/http_parser.h" // Works
Really the paths are not targeted correctly and the libraries are not portable. Is this a PIO problem or a problem with this particular library ?
The text was updated successfully, but these errors were encountered:
valeros
No branches or pull requests
Original issue raised here : https://community.platformio.org/t/lib-deps-include-paths-are-messed-up/13827
I added a library to platformio.ini : lib_deps = mbed-http
Great so it downloaded the dependency, with the structure:
– http_parser.c
– http_parser.h
– http_request.h
– http_request_builder.h
– etc…
(I think http_parser is a dependency of mbed-http)
However, if I want to include the library in my project, I need to use fully qualified paths :
But I also need to go into the library and change the internal library dependencies, so in http_request.h:
Really the paths are not targeted correctly and the libraries are not portable.
Is this a PIO problem or a problem with this particular library ?
The text was updated successfully, but these errors were encountered: