Hello,
My company has been testing out the CODEC2 library for potential use. Our
application of the CODEC2 library would be in an embedded system that is used
for lone worker safety.
Going over the LGPL 2.1 license one of the clauses is potentially problematic
for us. Sections 5 and 6 require that we provide a way for an end user to be
able to recreate the final executable using a modified version of the library
if they want to. I realize that we don't have to provide the source code itself
but my company would never allow the release of our binary files either. I'm
not 100% clear if our final firmware compilation (SREC or HEX) qualifies as an
executable file as it can't run on a generic OS.
Just wondering if anyone can comment on whether or not just linking the library
(with 0 modifications) statically with our firmware would require us to release
binary objects of our main firmware?
Thanks,
Marko
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
