Hi. > 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?
Yes if it is linked statically then you have a derivative work based on the library. The reason to provide the object files is that someone can change the code of the library in the the final product. This makes sense as hardware/software often exists for a long time even after the company that created it vanished. So if there is a major security bug in the open source library then the end user could fix it itself and is not dependant of a (probably not existing anymore) company to update it. I suppose replacing the library in the firmware directly is not really possible and therefore does not comply with the lgpl if no object code is provided.. > 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. But it's not random data, it's executable binary code that can be executed by a specific hardware; and an executable binary is also an executable. An Operating System is not needed for something to be an executable. I don't know how many people developed the library, but a license change you are asking for would need to be ratified by every developer that provided code for the library. Greetz Si Am 12.01.2018 um 22:23 schrieb Marko Milutinovic: > 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. > > > > > > > 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 > ------------------------------------------------------------------------------ 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
