Howdy On 12/01/2011, at 11:11 PM, Paul Coolwind wrote:
> In this case it will be very easy for anyone to bypass GPL: simply release > the core as DLL. Only if you started with fresh code. The GPL applies to code. So yes, you could write code, release it as a DLL, and not open source it. Your own code of course, not any other code taken or derived from existing GPL. So no, it is not bypassing GPL. Now it is a grey area of course. If you take a project and extend the project then you would be using the original code/concepts. But if you had for example a proprietary DLL to access special hardware, or even do a patented / commercial calculation, and release that as a DLL then it is understandable. It is grey, because technically GPL is supposed to only link in GPL. This has been argued a lot in Linux where people have released proprietary compiled kernel modules for video cards etc. But in the case of Win32 programming you have to load lots of non-GPL DLLs. So murky :-) Not black and white. > I too need those sources to be part of the LK 2.0 distribution, and I have > asked for them since months, while the 5.2.4 version was still distributed. Sorry, but they are not open source. Like many other DLL that you link to. You can download the DLL though. You should be able to link in and use the DLL. The DLL is still distributed, but I don't believe the code can be, without loosing its purpose (ie. to upload approved IGC files to OLC). How this is going to apply in the future, and new platforms ? Not sure. Scott ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
