This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: athttpd update
>>>>> "Oyvind" == =?UTF-8?Q?=C3=98yvind Harboe?= <oyvind.harboe@zylin.com> writes:
>> 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.
Oyvind> The two ways that come to mind are:
Oyvind> - use the objloader. Not saying it's easy, but it is
Oyvind> another fairly general approach to allow bugfixing of LGPL
Oyvind> libraries.
Objloader only supports a subset of the eCos architectures. It would
also require the use of a full-blown filesystem like jffs2 or yaffs.
Something like ROMFS embedded in the application executable would not
be good enough since there would still not be any way to replace the
libmicrohttpd object file. Even then the effort involved would be
non-trivial.
Oyvind> Reading over LGPL, the efforts to make the end-user
Oyvind> bugfixing possible can't really be postponed any longer
Oyvind> than up to the point where the binaries are
Oyvind> "distributed"(i.e. sent out of the house essentially).
Sorry, but no. The LGPL does not have any "where practicable" opt-out
language. Developers must abide fully by the terms of the license,
including allowing end-users to relink the application. If a developer
cannot abide by the terms of the license then the product cannot
legally be shipped to end-users.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
>>>> Visit us at ESC-Boston http://www.embedded.com/esc/boston <<<<
>>>> Sep 22-23 on Stand 226 at Hynes Convention Center, Boston <<<<
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss