Re: dual licensing try 2

> > If you really want to be able to interface mplayer to
> > closed source stuff - then just make every module dynamically
> > loadable (that's what I have done in my professional work).
> 
> Dynamically loading GPL code does not get around the GPL. If your
> proprietary program is using the GPL code, it must be fully GPL or (a
> technicality here) you must refrain from distributing the GPL'd code
> AT ALL (since you have forfeited your rights under the GPL by not
> releasing your program under the GPL).

I meant loading proprietary libs from GPL applications, the way
mplayer loads windows DLLs. If all parts of MPlayer were dynamically
loadable it would be easy to mix proprietary modules with non
proprietary as long as the core (module loader) was still GPL. I guess
this is what is commonly called the gray area of GPL, and the loophole
which allows driver writers to release closed source drivers for the
Linux kernel for example.

> Rich

//Anders