From: Marcel Holtmann <marcel@holtmann.org>
To: hoene@uni-tuebingen.de,
BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: ekiga-devel-list@gnome.org
Subject: Re: [Bluez-devel] Common file "sbc.c" in Ekiga/Opal and Bluez
Date: Thu, 30 Oct 2008 19:06:26 +0100 [thread overview]
Message-ID: <FF3DF936-BA45-4C47-9943-B0FD94903747@holtmann.org> (raw)
In-Reply-To: <006e01c939fe$19bf65a0$4d3e30e0$@hoene@gmx.net>
Hi Christian,
>> can we first talk about you statically linking MPL and LGPL code
>> together. This doesn't look like a good idea to me.
>
> Actually, it is the SBC codec plugin for Opal that is loaded
> dynamically.
> Does this make things better or worse?
that should be fine, but you need to put LGPL on the parts you wrote
to include the SBC routines and make them work.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-10-30 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 11:02 [Bluez-devel] Common file "sbc.c" in Ekiga/Opal and Bluez Christian Hoene
2008-10-29 18:41 ` Marcel Holtmann
2008-10-29 19:39 ` Christian Hoene
2008-10-30 18:06 ` Marcel Holtmann [this message]
2008-10-31 0:04 ` Craig Southeren
2008-10-31 7:09 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FF3DF936-BA45-4C47-9943-B0FD94903747@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=ekiga-devel-list@gnome.org \
--cc=hoene@uni-tuebingen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox