If you modify the stockfish code to create a dll and you are going to distribute that dll, then you should also provide the source code with the changes made in stockfish to create that dll if you have needed to modify the code of the files because you might fix it by adding new ones. The new code must of course be open source and GPL licensed.Michel wrote: ↑Fri Jan 22, 2021 12:11 pm
What you are saying makes no sense. What you are saying is that I can create a shared library "stockfish.dll" and then release a closed source chess engine that links against stockfish.dll. After all: I am not modifying the Stockfish source code so I have obligations towards the Stockfish authors.
Have you followed my advice and Googled for LGPL?
When Pocket Fritz used Fruit as a dll, they provided on request the code they used to convert Fruit into a dll, I think I remember it was 2 files. Of course they did not provide the source code for the GUI (Pocket Fritz).
I am giving you real examples that have already happened.
From there, nothing prevents you from creating a closed source engine that accesses that dll.
You can distribute your engine without providing source code. If you are going to distribute the stockfish dll, then also provide the new stockfish code that creates the dll.
About LGPL, I have nothing to say.
Sorry, my English is very poor, I don't know how to explain this to you better. Besides I think you are not in the mood to listen to my opinion and my reasoning. So I'll stop here.