You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was hoping to use this in my MIT licensed project, but unfortunately the LGPL license would cause me to have to license the final binary I distribute as LGPL, if I statically link. Would you consider adopting a license that doesn't force other projects to use the same license/is non-viral?
One approach you could consider is dual licensing as MIT and Apache 2.0, just like rustc itself and most of the rest of the rust ecosystem.
The text was updated successfully, but these errors were encountered:
Hi, I was hoping to use this in my MIT licensed project, but unfortunately the LGPL license would cause me to have to license the final binary I distribute as LGPL, if I statically link. Would you consider adopting a license that doesn't force other projects to use the same license/is non-viral?
One approach you could consider is dual licensing as MIT and Apache 2.0, just like rustc itself and most of the rest of the rust ecosystem.
The text was updated successfully, but these errors were encountered: