On 2023-09-18 13:08, Alan C. Assis wrote:
The thumb rule when starting with NuttX is using an existent
configuration as base.
OK.
Unfortunately the menuconfig is not prepared (better say it cannot) to
fix all dependencies for an driver or application (because of the
flexibility to use things in different ways on NuttX).
Yes. I found Kconfig quite fragile.
My hope was that selecting the basic interpreter in menuconfig would
result in a working basic interpreter as this option exists in the base
NuttX release.
NuttX boots fine and `nsh` runs. A CLI console based interpreter should
be no problem as no extra drivers are required.
I tried building on x86 Linux, but with the same result -- working nsh
but failing bas & scheme. `nm -u` shows both interpreters need to be
linked with libm.
I just have no idea how the NuttX build system specifies link libraries,
i.e. how to link an application with libm.
I will keep at it. Thanks for the help.
-KenD
