At Wed, 12 Sep 2001 16:09:16 +0100,
Phil Thompson wrote:
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:[EMAIL PROTECTED]]
> > Sent: 12 September 2001 16:08
> > To: '[EMAIL PROTECTED]'
> > Cc: Paul Davis; Phil Thompson
> > Subject: Re: [Alsa-devel] User Space Device Driver
> >
> >
> > At Wed, 12 Sep 2001 09:56:15 -0400,
> > Paul Davis wrote:
> > >
> > > >> alsalib is released under the GPL. hence, any
> > applications that to use
> > > >> it must be under the GPL. since such an application
> > would clearly be
> > > >> utterly designed around the alsalib and alsa kernel API,
> > you could not
> > > >> use dynamic linking to circumvent this.
> > > >
> > > >As alsalib is released under the LGPL, apps that use it
> > don't need to be
> > > >under the GPL.
> > >
> > > Oops. The source code is actually under mixed licenses. I looked at
> > > alsa-lib/src/output.c, for example. Looking inside
> > alsa-lib/src/*/*.c,
> > > it seems to be all LGPL.
> >
> > I guess it's just the result of wrong copy & paste...
> > IIRC, it was confirmed on ML that alsa-lib is under LGPL.
> > So all library codes should include LGPL declarations.
>
> Does that include the OSS compatibility library that is currently under the
> GPL?
It's GPL as long as taking a look at the code. In the above I mean
alsa-lib only.
But alsa-oss is not linked usually but pre-loaded. How is this case
handled? This seems obviously not restricting the apps or user device
driver at all from legal issue.
ciao,
Takashi
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
