The LesserGeneral Public License is sometimes described as a “weak copyleft” license, because code licensedunder LGPL’s terms can be combined with code under non-free licenses, and is sometimes used in thatfashion.10.1 The First LGPL’d ProgramThe first example that FSF encountered where such altered tactics were needed was when work began on the GNUC Library. The GNU LesserGeneral Public License (“GNU LGPL”) was designed as a solution for such situations. In particular situations, even those of us with the goal of building a world where allpublished software is Free Software realize that full copyleft does not best serve us. Our goal in designing the GPL was tomaximize its use of the controls of copyright law to maximize the number of works that were covered byGPL.However, while the strategic goal of software freedom is to bring as much Free Software into theworld as possible, particular tactical considerations regarding software freedom dictate different means.Extending the copyleft effect as far as copyright law allows is not always the most prudent course inreaching the goal.

Toggle navigation.Chapter 10The Lesser GPLAs we have seen in our consideration of the GPL, its text is specifically designed to cover all possiblederivative, modified and/or combined works under copyright law. But, it is possible to comply even with static linking – simply make your.obj files (either separate or bundled into a.lib) available, and the user can then link this with the desired version of the LGPL library. It’s easiest to comply by dynamically linking to the LGPL library, since the user can then just substitute the DLLs at runtime. It does not prohibit you from building with an ultra expensive and rare compiler It only says the user must be free to substitute a different version of the LGPL library to work with your program. The LGPL doesn’t discuss anything about which toolset is used. For that to work properly, both the DLL and the calling EXE must be built with the same C compiler version, they must be both dynamically-linked to the same flavor of the CRT, etc.

Unfortunately, this theory is not always true in practice.In particular, let’s consider the case of an LGPL library written in C, built as a DLL on Windows, and exposing a C interface that uses some STL classes. As we saw, this is a highly-constraining design.

Chom lo hont tere mp3 song