casaroli opened a new pull request, #19940: URL: https://github.com/apache/nuttx/pull/19940
## Summary `apps/examples/fdpicxip` is in apps master and its `modules/Makefile` reads `$(NUTTX_DIR)/tools/fdpic/nuttx-fdpic.mk` and `$(NUTTX_DIR)/tools/fdpic/fdpic-embed.py`, which are not in this tree, so its committed module blobs cannot be regenerated. This adds what that Makefile names. `nuttx-fdpic.mk` builds a module: compile with the stock `arm-none-eabi` GCC, which emits correct FDPIC objects for C and C++, then assemble and link with an `arm-uclinuxfdpiceabi` binutils, which is the only piece a distribution does not carry. `build-binutils.sh` builds that, and takes about a minute. `nuttx-exports.sh` turns a built firmware's `exec_symtab.c` into a symbol list, `fdpic-verify.sh` checks a module's imports against it, and `fdpic-embed.py` turns a module into a C header. `Documentation/components/tools/fdpic.rst` describes them under Host Tools, where the tools index picks it up by glob. This answers @cederom's request on #19673 to move the tool README into the documentation. This is the third of four independent pieces split out of #19673, so each can be reviewed on its own. The others are `[1/4]`, `[2/4]` and `[4/4]`. They do not depend on each other and can merge in any order. ## Impact Host side only. Nothing in the NuttX build calls these tools, no `Kconfig` option selects them, and no target code changes. The loader that runs what they build is proposed separately, so a module built here has nothing in NuttX to load it yet. The page says so. ## Testing `make html` in `Documentation/` produces no warning for the new page. The local build fails on pre-existing duplicate C declarations and a missing `plantuml`, neither related to this change. `tools/checkpatch.sh` passes. These are the tools that built the module blobs committed in `apps/examples/fdpicxip`, on macOS with the `arm-uclinuxfdpiceabi` binutils 2.43 that `build-binutils.sh` builds. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
