GPL, LGPL, other Licences

Blaze1st · 01-17-2003, 11:46 AM

Hi!

I'm woindering about if I write and compile a program with a GPL IDE and Compiler, then should I publicate it under GPL or I could choose its licence?

How can I make binary only programs for linux, if my customer wants it to be only his/her, and not open?

Thanks!

Blaze1st

rshaw · 01-17-2003, 11:57 AM

you can use gpl'ed tools to create a non-gpl'ed app, no problems. microshaft would have you believe that everything the gpl touches has to be released under the gpl, thats a total falsehood.

Blaze1st · 01-17-2003, 04:07 PM

Thanks!

For example if a school order an administrator application from me, and they want it to be binary only, (don't want the students to find the code and hack it some way) then I can use GPL tools and publicate the program with MyLICENCE, if it doesn't contain any part of GPL code?

rshaw · 01-17-2003, 04:11 PM

exactly.

rshaw · 01-17-2003, 04:26 PM

if you need/want to use gpl'ed libraries(no sense in re-inventing the wheel), just link to them dynamically (as opposed to statically)and there will be no gpl issues either.

Blaze1st · 01-17-2003, 05:21 PM

Thank you for your help!

mhearn · 01-18-2003, 09:37 AM

Actually if you link to a GPLd library, your code must also be GPLd.

You can use GPLd tools to do whatever you like, and you can incorporate LGPLd code into your own code, but if you use GPLd code then your product must also be GPLd.

trickykid · 01-18-2003, 11:15 AM

I believe this is covered under the GNU Lesser General Public License, sections 5 and 6.

http://www.gnu.org/copyleft/lesser.html

Blaze1st · 01-18-2003, 01:46 PM

Hi!

I'm not a jurist, so I could read these licences for good.

So can you tell me how should I licence when I use a dynamically linked library, and a statically linked library in case of GPL'd and LGPL'd libraries.

Thanks!

mhearn · 01-18-2003, 02:27 PM

If you use a library under the GPL you must make your own software GPLd too. This is the case regardless of how you link to it.

The LGPL does not have that clause, you can write proprietary software with it. If you alter the library itself though you must still contribute the changes back

rshaw · 01-18-2003, 04:26 PM

use it inhouse and never release it and you won't have to licence it gpl

rshaw · 01-21-2003, 12:41 PM

i stand corrected. after re-reading the gpl and the gpl-faq, the condition i had in mind only applies in a very narrow number of circumstances. if you use gpl'ed libraries you ...WILL... need to gpl the entire program... IF ... you sell, give away, or distribute it in any way. if you use the finished application internally, (home,school,or company use) and never release it,then you are not bound by the gpl to licence the antire app. as gpl'ed

thanks for keeping me on my toes mhearn, and sorry for causing any confusion.