tinnedkarma opened a new issue, #17323: URL: https://github.com/apache/nuttx/issues/17323
### Description Hello all, Been reading the docs lately, both the "new" one (the one in the current nuttx tree) and the old one (https://cwiki.apache.org/confluence/display/NUTTX/Nuttx). There is detailed documentation about nxflat, reasoning, usage, pros/cons. But, looking at what is currently in the nuttx tree makes me wonder if it is still supported, or completely abandoned. * ``binfmt`` had two distinct directories, ``libnxflat`` and ``libelf``. * the ``libelf`` currently resides in ``libs/libc/libelf`` (sometime ago it used to be called ``modlib`` if I'm not mistaken?) * ``libnxflat`` stays untouched in the ``binfmt`` dir, which led me to think there is no more interest for it * With the current suggested nuttx workspace layout, ``nxflat`` cannot be used. * The source code for ``nxflat`` can be added to the final nuttx target/bin file, but no tooling present to actually build the nxflat compatible file, that can be written to the device and loaded by the nuttx binary * Those tools still resides at https://bitbucket.org/nuttx/buildroot/src/master/, but the whole concept of buildroot toolchain seems scraped Outside the mailing list and other forms of mails, there is small to none additional info about the state of nxflat. So my question is, what happened to ``nxflat`` file format, seems deprecated or abandoned in the nuttx tree. Is it recommended for new designs, should we avoid it? If this is indeed the case, I would suggest at least mentioning this in the current documentation, or schedule it for removal, as it being present is misleading for newcomers. I could find much more documentation about nxflat compared to the elf alternative. ### Verification - [x] I have verified before submitting the report. -- 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]
