TimJTi commented on issue #16484:
URL: https://github.com/apache/nuttx/issues/16484#issuecomment-2940664897

   @patacongo thank you. If built-in apps can't be run as I suggested 
(/bin/appname) then I suspect they probably used to be able to. So:
   
   1. Current documentation is - not surprisingly - broken. It shows you should 
be able to do this. See 
[here](https://nuttx.apache.org/docs/latest/components/filesystem/binfs.html#binfs)
   2. thttpd with binfs may have worked at whatever point in time builtins 
*could* be run from a union fs mounted as /www/cgi-bin. There are 2 "demo" cgi 
apps there that get built in, but thttpd can't call them. Which I found out 
with my variant too, hence this issue being raised.
   3. I will plough through @acassis video and see if I can get my cgi scripts 
(aka applications) built as standalone elf files, mounted in the filesystem via 
ROMFS or something. This, in the long run, would be safer anyway, as we don't 
want all and any random builtin apps able to be run via a web page anyway!
   4. Looks like NXFLAT is dead. I could not get the tools built and installed: 
they are very old. Maybe if the actual executables (mknxflat and ldnxflat) 
could be included in the NuttX tools it would help! I might take a look and see 
if they could be made into python scripts or something.
   
   If I make it out of the other side of this alive, and with something 
working, I will do my best to update documentation as I have wasted WEEKS on 
this.
   
   But off on a 2 week holiday tomorrow so might be a while lol


-- 
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: commits-unsubscr...@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to