If someone would like to update athttpd in eCos CVS (so www.ecosforge.net athttpd can be retired) or take over maintenance for athttpd in ecosforge.net, then that would probably be welcomed.
I wouldn't want to put athttpd(or the dated eCos TCP/IP stack for that matter) directly onto the internet, but for in-house lan's and device configuration purposes it should be fine. > Specifically, those end users should > be able to fix a problem with libmicrohttpd, recompile it, and then > rebuild the entire eCos application with the fixed library. The two ways that come to mind are: - use the objloader. Not saying it's easy, but it is another fairly general approach to allow bugfixing of LGPL libraries. - ship some header files a linker library(which may be stripped of debug info) that allows rebuilding and linking the entire application. Reading over LGPL, the efforts to make the end-user bugfixing possible can't really be postponed any longer than up to the point where the binaries are "distributed"(i.e. sent out of the house essentially). -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
