Re: [Libusb-win32-devel] Licensing for USB Inf Creator / Installer and libraries

[Xiaofan C. <xia...@gm...>]

Do you mean that the developer uses libusbK GUI inf-wizard to create the
driver installer?

libusbK license: you can choose the BSD option (except portions using libwdi
which uses LGPL v3 license).
https://github.com/mcuee/libusbk/blob/master/libusbK/license/AUTHORS-libusbK.txt

The installer uses libwdi, which uses LGPL v3 license.
https://github.com/pbatard/libwdi

The installer does not modify libusb0.sys and libusb0.dll, so you do not need to
worry about the distribution of libusb0.sys (GPL v3 license) and libusb0.dll
(LGPL license v3)
https://github.com/mcuee/libusb-win32/blob/master/libusb/installer_license.txt

I can see the only issue seems to be the libwdi linkage of the libusbK
GUI installer tool
(which may force it to be GPLv3 licensed because of static linking).
However, I believe
the driver installer created by the tool does not fall into GPLv3
license. You do need to
mention the license of the components, like the license of
libusb0.sys/libusb0.dll and
libusbK.sys/libusbK.dll. You may also want to mention the driver
installer is created
using the libusbK GUI Inf wizard tool and its license.

Take note I am not a lawyer so you may want to talk to your legal department
with the above information which can not be considered as legal advice
but rather
my personal opinion.

Best regards,
Xiaofan

On Thu, Oct 10, 2024 at 6:38 PM Kilbane, Stephen
<Ste...@an...> wrote:
>
> Hi all,
>
> Is there information that outlines which licenses apply to which libraries?
>
> One of our developers is using USB Inf Creator/Installer, targeting WinUsb, libusbK
> and libusb0. Our OSS compliance processes identified a variety of weak/strong copyleft licenses.
>
> As I understand things – and I’m not the developer working with libusbK, so I may have
>  this wrong – the developer is using the Creator / Installer to create the libraries as well as
>  to install them. Given that there are multiple stages involved, I’m struggling to understand
> which licenses apply to the creator/installer, and which apply to the resulting libraries –
>  and since I’m not the developer working with this package, I’m not able to see where the
> boundaries lie between components, in the source tree.
>
> We’re keen to make sure we fulfil any and all licensing obligations, so ny guidance
> gratefully appreciated.
>
> Thanks,
>
> steve
>
> --
>
> Stephen Kilbane
>
> Director,
> Open Source Program Office
>
> Tel +44 131 346-3450
> Email ste...@an...
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel