Here are some contexts from LGPL v2.1
*if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights."Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.* On 29 November 2017 at 19:36, drwho <[email protected]> wrote: > > I don't think the "script which *calls* configure" is necessary, but > please be aware.... > > https://www.gnu.org/licenses/gpl-faq.en.html#InstInfo > > GPLv3 explicitly requires redistribution to include the full necessary > “Installation Information.” GPLv2 doesn't use that term, but it does > require redistribution to include "scripts used to control compilation and > installation of the executable" with the complete and corresponding source > code. This covers part, but not all, of what GPLv3 calls “Installation > Information.” Thus, GPLv3's requirement about installation information is > stronger. > > Jon > > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". > _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
