Comment Re:Addressing a few comments... (Score 1) 445
It is a very fine line. :-/
The line is drawn when you are resolving symbols in memory and therefore you can make direct calls to the GPL DLL from your software. This goes for LoadLibrary/GetProcAddress: you are resolving symbols in the DLL so that you can call them directly. That is linking, though at runtime.
Now, if you run a GPL executable, there is no symbol resolution BETWEEN your software and the GPL exe. No problem.
The memory mapped argument is still pretty clear (well, for me. :-P). You can modify the GPL'd executable to open shared memory and then use that as an interface to your application (a protocol proxy, basically). BUT, you must release the changes you made to the GPL'd executable to make that shared memory interface; your software does not need to be GPL. If this was a violation, we'd be screwed because web browsers would have to be GPL'd if they connected to a GPL'd web server.
The line is really the facility for linking, whether it be at compile-time (static) or run-time (dynamic).
-Scott
The line is drawn when you are resolving symbols in memory and therefore you can make direct calls to the GPL DLL from your software. This goes for LoadLibrary/GetProcAddress: you are resolving symbols in the DLL so that you can call them directly. That is linking, though at runtime.
Now, if you run a GPL executable, there is no symbol resolution BETWEEN your software and the GPL exe. No problem.
The memory mapped argument is still pretty clear (well, for me.
The line is really the facility for linking, whether it be at compile-time (static) or run-time (dynamic).
-Scott
