On 10/4/2023 8:02 PM, Gustavo Soares wrote:
Hi Greg!
Yes, if I use #include this problem is solved, but
then the code loses the reference to that specific struct causing another error.
And how exactly "the file does not exist"? I can open it and it is at the nuttx
repo, I shared it's link.
Actually, the problem is very simple. This file does not exist.
#include
You probably wanted
#include
The more I look at what you are trying to do, the more confused I get.
There is a file at drivers/ioexpander/pcf8575.h, but you are not
permitted to include that. That contains
Hi Greg!
Yes, if I use #include this problem is solved, but
then the code loses the reference to that specific struct causing another error.
And how exactly "the file does not exist"? I can open it and it is at the nuttx
repo, I shared it's link.
From:
Why wouldn't the compiler access nuttx/drivers/ioexpander/pcf8575.h?
Access to internal driver files by applications is specifically
forbidden. This is part of the enforcement of the modular design to
assure that people do not do that kind of thing: Applications must
not have access to
Why wouldn't the compiler access nuttx/drivers/ioexpander/pcf8575.h?
Access to internal driver files by applications is specifically
forbidden. This is part of the enforcement of the modular design to
assure that people do not do that kind of thing: Applications must not
have access to
On 10/4/2023 7:02 PM, Gustavo Soares wrote:
Why wouldn't the compiler access nuttx/drivers/ioexpander/pcf8575.h?
Access to internal driver files by applications is specifically
forbidden. This is part of the enforcement of the modular design to
assure that people do not do that kind of
