One of the next things we want to do is develop some front ends. QT is our
preffered method. Obviously we have to purchase a QT license, now I haven't
researched it, so I'll start by asking this here.
Do we need to purchase the license as a company to develop the code and sell
it, or do we need to purchase a license to develop and a license for every
copy sold? That would drastically raise the cost of our product.
I don't care for GTK+ much, so I would much rather go QT. Plus, a lot of our
stuff would preferably run in KDE, so it's better integration, and since most
KDE libraries are LGPL we are safe with them.
I really shouldn't have used the term 'viral'. I apologize for that. I
sincerely just meant to describe the way that binaries linked against GPL
must also be GPL. It's my ignorance and I'm sorry. Please no offense.
Nathan
On Thursday 30 September 2004 00:49, der.hans wrote:
> Am 29. Sep, 2004 schwätzte Nathan England so:
> > My company is having problems with the GPL. We are concerned about the
> > 'viral' effects of the GPL. Can we use GPL libraries in our software
> > without open sourcing it?
>
> The GPL is not 'viral'. It does not reach out and infect other stuff. The
> m$ license on not producing GPLd code w/ their compiler could maybe be
> seen as viral as that does affect things that aren't attached to it.
>
> Is your company using the code internally? Nothing in the GPL requires
> making code publicly available if the resulting programs aren't available
> publicly.
>
> An example I used last night is that even on my home use projects I tend
> to use the GPL. Most of it will never be seen my anyone but me, though. I
> don't release the program, so I don't have to release the code.
>
> > Are there libraries we can use that aren't GPL?
>
> Look at LGPL. It doesn't require release of code that links against it.
>
> *BSD/MIT/Apache/Mozilla style licenses don't require release of code in any
> way.
>
> > We are 75% linux oriented, but would like a library that could cross OS
> > boundaries. Are there any GPL libraries we could do that with, without
> > open sourcing our code?
>
> There are many options, depending on what you're doing and what the
> company's needs are. One thing you can do is to develop using Trolltech's
> QT, then pay Trolltech to use their licensed version.
>
> > We would like to use a lot of GPL stuff, but are genuinely afraid of the
> > 'viral' effects.
>
> Then don't use stuff from m$, Apple, Adobe, etc. :)
>
> ciao,
>
> der.hans
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)