Lpc2000

Tom Walsh wrote:

>seangra wrote:
>
>  
>
>>AFAIK you're not correct there.  If I take GPL code I only need to 
>>make source code available if I have modified the GPL'd code itself.  
>>Even in that case I only have to make available the modified code, not 
>>my entire code base.  Locally we've been using GPL'd code for a while, 
>>we keep it in a seperate library and since we have modified it, the 
>>library source is available, but not the source to our entire 
>>application.
>>
>> 
>>
>>    
>>
>No, read the license discussions on other websites.  If you statically 
>link proprietary code to GPL code, then you must release source, if you 
>dynamically link at runtime, then you do not have to distribute source 
>of your application.  However, you must distribute the object files of 
>the proprietary application.
>  
>
Correction on my part: LGPL static linking requires object modules to be 
available from the proprietary app. Not GPL, in either case where you 
dynamically link at runtime, you can protect your proprietary source.  
Static linking is where the problems can arise.

Regards,

TomW



>Open Source Software does place some obligations on you.  You simply 
>cannot say "oh, but I download the source, so it is now mine to do what 
>I please with it".  Some OSS you can do that, as per their license, not 
>with GPL.
>
>TomW
>
>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------