Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License clarification (relating to libulz) #2

Open
therontarigo opened this issue Feb 13, 2023 · 1 comment
Open

License clarification (relating to libulz) #2

therontarigo opened this issue Feb 13, 2023 · 1 comment

Comments

@therontarigo
Copy link

therontarigo commented Feb 13, 2023

tinycpp has standard MIT license terms, but uses three header files from libulz, which is available under LGPL license.

It appears to be true that from libulz headers, tinycpp

uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length)

(LGPL Version 2.1 Terms and Conditions Section 5, paragraph 4), in which case LGPL adds no restrictions to tinycpp. Is this the case?

Otherwise, tinycpp object code would be effectively LGPL, which is why I'm asking for clarification. A relicensing of the three libulz headers themselves to MIT (which is LPGL-compatible) would resolve this most simply.

@rofl0r
Copy link
Owner

rofl0r commented May 12, 2023

i've been meaning to replace the hashtable implementation used in tinycpp for a while, that's why i didn't make a move yet. but you're right, the headers should be using MIT too. i'll see what i can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants