Hi Bruce and Si,
Thank you for the responses. I’ll take this info back and discuss with my group.
Another caveat is that we use a proprietary tool chain for compilation and
linking (IAR). Without the end user having these tools it would be almost
impossible for them to re-link against a newer version of the library. In our
FW it would be impossible to replace the library unless an entire FW update was
performed.
Cheers,
Marko
From: Bruce Perens [mailto:br...@perens.com]
Sent: Friday, January 12, 2018 7:31 PM
To: freetel-codec2@lists.sourceforge.net
Subject: Re: [Freetel-codec2] Licensing question
Hi Marko, sorry to do this from my phone but I won't be at my desk until
tomorrow. Your employer is not required to distribute the binary program of
your proprietary code but you must make it possible for the end-user to install
a replacement of codec 2 when it's upgraded. Other manufacturers presently do
this flexradio is an example. I can go over with you further on the phone what
would you be compliant with the license and what wouldn't, no charge for the
call.
Thanks
Bruce
On Fri, Jan 12, 2018, 16:57 Marko Milutinovic
<mmilutino...@blacklinesafety.com<mailto:mmilutino...@blacklinesafety.com>>
wrote:
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<mailto:Freetel-codec2@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
------------------------------------------------------------------------------
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
