> Since OpenOCD ist gpl-v2-or-later, loading non-GPL-compatible DLLs is > problematic
Not if it's only for private use and not for wider release/distribution. It's not clear which use is intended in this case. https://www.gnu.org/licenses/gpl-faq.en.html#:~:text=The%20GPL%20does%20not%20require,privately%2C%20without%20ever%20releasing%20them. ________________________________ From: cw...@thedigitaledge.co.uk <cw...@thedigitaledge.co.uk> Sent: Thursday, October 7, 2021 11:28:41 AM To: openocd-devel@lists.sourceforge.net <openocd-devel@lists.sourceforge.net> Subject: Re: Porting the P&E Multilink Universal adapter On Wed, 2021-10-06 at 13:06 +0200, Michael Schwingen wrote: > On 06.10.21 12:15, cw...@thedigitaledge.co.uk wrote: > > All, > > > > I'm currently trying to port P&E Multilink Universal[1,2]. This is > > currently supported by pyocd-pemicro[3] using external dll[4]. > > What license applies to these DLLs? > https://github.com/NXPmicro/pypemicro specifies "bsd 3-clause", does > that include the binary-only DLLs? I the Source for those DLLs > available? > > Since OpenOCD ist gpl-v2-or-later, loading non-GPL-compatible DLLs is > problematic - I think we had this discussion earlier (with the FTDI > libraries?). > If the licensing is a problem in the long term would I be able to release a separate package with the drivers in to get around the bsd licensing issue. My question still stands on how I would go about getting the hal to be compiled on my system. Thanks, Chris
