GPL exception clarification #582
GeorgePriestner-Eaton
started this conversation in
General
Replies: 1 comment 1 reply
-
The method of linking does not matter for GPL-2.0-or-later WITH GCC-exception-2.0 license. Note: GPL-2.0-or-later WITH GCC-exception-2.0 license only applies to the core BACnet C modules used for encoding/decoding/state-machine-operation. Every file includes a copyright and their specific license in the file header. See also a task to convert all the text license info to SPDX format: #55 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @skarg,
I had a question about the GPL license the bacnet-stack is registered under; the exception states:
This BACnet protocol stack implementation is specifically designed for the embedded BACnet appliance, using a GPL with exception license (like eCos), which means that any changes to the core code that are distributed are shared, but the BACnet library can be linked to proprietary code without the proprietary code becoming GPL.
Does it matter which method of linking is used? I.e. we are looking to use in Zephyr (RTOS) and so would be statically linked (not dynamically linked) to our proprietary code.
Thanks!
cc @gregshue
Beta Was this translation helpful? Give feedback.
All reactions