Page 1 of 1

License unclear on what a "Wrapper DLL" qualifies as

Posted: Wed May 07, 2025 3:18 pm
by Quin
Hi Fred,
The PureBasic license states this:
The PureBasic license explicitly forbids the creation of DLLs whose primary function is to serve as a 'wrapper' for PureBasic functions.
However, this is unclear. I wrote a DLL for use in a programming language with very limited library support, and its primary purpose is rendering game maps. However, this language doesn't have FTP support, so I thought about adding some ftp functions to my DLL. However, they'd basically just wrap the internal PB functions, so is htis allowed? It's not eh main purpose of my DLL, just a side feature, but the license is unfortunately unclear here.
It does say "primary purpose", but that's fairly subjective. Someone could only want my dll for the FTP functions, even if that's not the main reason I wrote it.
Thanks!

Re: License unclear on what a "Wrapper DLL" qualifies as

Posted: Wed May 07, 2025 3:52 pm
by Fred
If you want expose FTP functions for a DLL which will be redistribuable, you can write more high-level function for your specific needs. Just wrapping all the FTP lib individuals commands is not allowed as you could then expose the whole PB commandset for free.

Re: License unclear on what a "Wrapper DLL" qualifies as

Posted: Wed May 07, 2025 4:07 pm
by Quin
Gotcha, so the license prohibits me from exposing FTP functions as PB does, but I can still call into the FTP APIs and let users of my library use them?
That's pretty much what I'd expect, but the last thing I want is to violate the license of this amazing tool you've spent 25+ years working on. To quote a now sadly defunct forum member: "I may look like a mule, but I'm not a complete ass."