LGPL library porting and license?

Question

Software porting

Hello. Suppose there is a library under the LGPL license in one language, if I port it to another language, do I have to use the LGPL license or can I use any?

Answer 1

First, a little terminological clarification:
Usually, the term "port" means a well-defined process. Adapting running code to another OS or other hardware platform. Those. for example, you have a library that works on x86/x86_64 but doesn't work on other platforms. You take and “finish” a dozen or a hundred lines of code, after which this library begins to magically build for ARM. At the same time, the library remains what it was, including under the same LGPL license, it will simply include your patch.
However, if I understand you correctly, are you going to write some code in another programming language that implements similar functionality? But in this case, there is no question of any "porting". Accordingly, you write 100% your own code, under your own license.
Or you want to make a language binding (that is, a “body kit” around an existing library) to call library functions from another language. But in the case of a "language kit", you do not modify the LGPL library itself, but write code that simply calls functions from it. And LGPL allows it (LGPL libraries can be used in proprietary projects as is).

Answer 2

As far as I understand, it should also be under lgpl. But the fact that it will link with it is possible without lgpl.

Answer 3

There is a discussion on SO - it seems that yes. This is a derivative work (derivative), and this is exactly what is stipulated in the LGPL-license.

Answer 4

If you want to make your implementation of this library compatible with the API, then so that there are no complaints against you, all you can use is the description of the API, but you cannot look at the source codes.