Thank you Ali,

There are only several people interested in C++ on NuttX, sorry. Can
you please report Issue on github [1]? Can you also provide a fix
patch as PR on github? Please attach your build host details such as
OS type/version, compiler type/version, etc :-)

Thanks :-)
Tomek

[1] https://github.com/apache/nuttx/issues

On Sun, Jul 27, 2025 at 6:52 PM Ali M. Mansoory K.
<alim.manso...@gmail.com> wrote:
>
> Dear Apache NuttX Team,
>
> I was following the C++ and CMake guide
> <https://nuttx.apache.org/docs/latest/guides/cpp_cmake.html> from your
> documentation, and I encountered several issues that I believe may be due
> to changes in the folder structure or recent updates in the repository.
>
> Specifically:
>
>    1.
>
>    After running make export, I received the following error:
>
>    nuttxspace/nuttx/libs/libc/elf/gnu-elf.ld': No such file or directory
>
>    It appears this path or file no longer exists or has been moved.
>    2.
>
>    When building the project, it failed with an error related to missing
>    cstdio. I noticed the CMakeLists.txt refers to:
>
>    ${NUTTX_PATH}/include/libcxx
>
>    However, this directory seems to have been renamed or replaced—libcxx no
>    longer exists, and I found a cxx directory instead. After adjusting the
>    path, the next build error occurred:
>
>    error: 'string' was not declared in this scope; did you mean 'stdin'?
>    src/HelloWorld.cpp:18:9
>
>    It seems the standard C++ header <string> could not be found. This might
>    indicate missing include paths or incorrect configurations for C++ standard
>    library support in the example.
>
> Based on these issues, I believe the guide could benefit from an update to
> align with the current repository structure and build process.
>
> Please let me know if there are updated instructions elsewhere or if I can
> assist in clarifying the problems I encountered.
>
> Thank you for your time and for the great work on NuttX.
> --
> Yours truly,
> Ali M. Mansoory K.



-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Reply via email to