3 ms·
This appears to be the case in the EU (although the is no case law yet). According the this article [1] of the EU "linking two programs does not produce a singl
by cmitsakis 4y ago
This appears to be the case in the EU (although the is no case law yet). According the this article [1] of the EU "linking two programs does not produce a single derivative of both (each program stay covered by its primary licence)" because Directive 2009/24/EC allows this: "any portion of code that is strictly necessary for implementing interoperability can be reproduced without copyright infringement".
Even static linking might not create derivative works. The method of linking is just a technical detail that is not relevant.
[1] https://joinup.ec.europa.eu/collection/eupl/matrix-eupl-compatible-open-source-licences#section-3 https://joinup.ec.europa.eu/collection/eupl/matrix-eupl-comp...
- kazinator 4y agoEven if we suppose that static linking creates a derivative work, you can deliver the program in an separated state (e.g, collection of libwhatever.a files for a Unix-like system). We could write a linker (or modify one) such that it provides an execution service: it loads specified object files and archives into memory, resolves them and then without dumping a program image, just executes it. Then static linking effectively becomes a form of dynamic.