From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ development In-Reply-To: <0FA9D595-36DD-4499-92B1-7C7080955B55@mac.com> References: <1165753987.22251.6.camel@aeonflux.holtmann.net> <0FA9D595-36DD-4499-92B1-7C7080955B55@mac.com> Date: Sun, 10 Dec 2006 20:49:26 +0100 Message-Id: <1165780166.11292.0.camel@localhost> Mime-Version: 1.0 Subject: Re: [Bluez-devel] Using BlueZ Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Brian, > >> I would like to know if its possible to use the BlueZ stack with > >> something that has a GPL incompatible license? i.e. MPL? I noticed > >> that its GPL licensed which limits its usage with such projects. Any > >> alternatives? > > > > if you have to link against the Bluetooth library, then the answer is > > no. If you only use the D-Bus interface of BlueZ, then you link > > against > > the D-Bus library and this one is LGPL, so that is no problem. However > > you should always double check with "ldd" what libraries are actually > > linked in or if you include header files from "bluetooth/*.h". Make > > sure > > you don't link against the Bluetooth library and you are good. > > Do you loose any functionality vis D-Bus? depends on what you need to do. Describe your use case and I might be able to tell you. Regards Marcel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel