So, in Kconfig, Example/popen should "depends on" FIFO and named pipe drivers?
On Wed, Dec 20, 2023 at 2:08 PM Alan C. Assis <acas...@gmail.com> wrote: > That is because you forgot to enable: > > Device Drivers ---> > [*] FIFO and named pipe drivers ---> > > Remember: "git grep" is your friend! > > BR, > > Alan > > On Wed, Dec 20, 2023 at 9:53 AM Gustavo Soares < > gustavo.felipesoa...@hotmail.com> wrote: > >> Hi Alan! >> >> Yes, this message pops up when trying to compile: >> >> the problem seems to be in the apps/system/popen. >> Should any other configuration be applied besides enabling the >> popen()/pclose() functions? >> >> ------------------------------ >> *De:* Alan C. Assis <acas...@gmail.com> >> *Enviado:* quarta-feira, 20 de dezembro de 2023 08:15 >> *Para:* dev@nuttx.apache.org <dev@nuttx.apache.org> >> *Assunto:* Re: Read response from console >> >> Hi Gustavo, >> >> Do you mean apps/examples/popen is not working? >> >> I remember using popen() in the past to get the result of other program >> output. >> >> Best Regards, >> >> Alan >> >> On Mon, Dec 18, 2023 at 3:39 PM Gustavo Soares < >> gustavo.felipesoa...@hotmail.com> wrote: >> >> Hello everyone! >> >> I have some i2c devices connected to my ESP32 and I can get their values >> by using the i2c get command from NuttX. Now I need my app to extract the >> value from the response, so I enabled the popen() and pclose() functions >> but it still not possible to use them, is there any other config that must >> be enabled? Even the popen example can't find the method reference. >> >> >> BR, >> Gustavo. >> >>
