btashton commented on issue #3737:
URL: 
https://github.com/apache/incubator-nuttx/issues/3737#issuecomment-842705501


   > 
   > > I was actually investing some stuff related to nxflat over the weekend 
   > > to try some thoughts I had on improving the share module story.
   > >
   > I have already implemented full, MMU-less shared library support in a 
   > binary format that call XFLAT.  You can see that code at 
   > http://xflat.sourceforge.net/ (haven't touched that in years). The 
   > Sourceforge code is still under CVS!  There is a GIT version here: 
   > https://bitbucket.org/patacongo/xflat/src/master/
   > 
   > I created NxFLAT as a stripped down version of XFLAT with no shared 
   > library support but with a smaller footprint suitable for the kind of 
   > MCUs that NuttX originally target.
   > 
   > The objectives of NuttX have changed over the years.  Originally, it was 
   > intended to be a tiny RTOS with size comparable to the other tiny RTOSs 
   > like FreeRTOS and ChibiOS, but still supporting mostly POSIX OS 
   > interfaces.  So a lot of corners were cut in the original designs to 
   > keep the size to a minimum.  That objective has morphed over the years:  
   > Now we aim to be small (but not tiny) Linux work-alike.  Very different 
   > concept.
   > 
   > 
   
   Not to derail this issue, but what I'm actually wanting to be able to do is 
support loading elf files on some of these smaller chips without a mmu, but 
keep the memory usage down by not having to have a bunch of copy of libc 
included.
   
   Some of the compiler flags to help make this possible do not seem to exist 
outside of ARM, but there was some recent interest in adding support for RISCV 
gcc.
   
   I'll read more of the xflat docs / design.
   
   But back to your question @a-lunev please do try the flag we suggested I'm 
motivated to help remove any roadblocks you run into and maybe I'll spend some 
time updating the docs.


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to