Replies: 3 comments
-
Unfortunately, I can't provide legal advice. I can confirm that the CSWin32 tooling is distributed under the MIT license, and the metadata it's designed to consume (https://www.nuget.org/packages/Microsoft.Windows.SDK.Win32Metadata) is distributed using the Microsoft Windows SDK license (https://aka.ms/WinSDKLicenseURL). With regard to compatibility with the GPL, you'll want talk to legal counsel that can discuss your particular situation. Thanks, Ben |
Beta Was this translation helpful? Give feedback.
-
Non-authoritative answer: As you seem to already have determined, the more relevant license for your concern is probably the one associated with the metadata. The metadata doesn't ship with your app either. But your app takes a dependency on Windows DLLs as a result of using CsWin32, just as it would if you had hand-written the interop. I'll see if we can get an authoritative answer added to our license or readme files. |
Beta Was this translation helpful? Give feedback.
-
Many thanks for the answer! If I understand correctly, CsWin32 is a build tool just as Visual Studio is. The GPL has an exception called "System Library Exception" that is explained here: |
Beta Was this translation helpful? Give feedback.
-
CsWin32 has the MIT licence, but it depends by the Windows.SDK that has its own licence.
I know the MIT licence is compatible with the GPL, but I don't know if the Windows.SDK licence too.
I am not an expert in licensing, so I ask those who know more about it:
Can I use the GPL licence for my application if it use CsWin32 and its dependencies?
Beta Was this translation helpful? Give feedback.
All reactions