Return-Path: Message-ID: <45AC53A0.5040701@xmission.com> Date: Mon, 15 Jan 2007 21:25:04 -0700 From: Brad Midgley MIME-Version: 1.0 To: BlueZ development References: <44F6B7AE.1030209@jambit.com> <4582A310.60905@jambit.com> <4583A020.2040808@xmission.com> <4587D051.8080703@jambit.com> <458864F1.4070104@xmission.com> <4589371F.2000507@palmsource.com> <45A54D5B.8030001@xmission.com> <45A5F6DD.7020904@palmsource.com> <45A7D8E0.20908@xmission.com> <7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6EBC@eumonex01.palmsource.com> In-Reply-To: <7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6EBC@eumonex01.palmsource.com> Subject: Re: [Bluez-devel] RE : How to use sbc.c ? 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 Frederic I don't think they should need to coexist. We'll choose one or the other and it'll create the same shared objects. They do need to stay binary/api compatible to pull that off though. >> How about if we create a separate cvs module like "sbc64" that contains >> libsbc with a 64-bit encoder? > > I fully agree! > Should the two library coexist? Brad ------------------------------------------------------------------------- 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