Return-Path: Message-ID: <28c817710607182109l7518990fqc45ea07198919363@mail.gmail.com> Date: Wed, 19 Jul 2006 12:09:56 +0800 From: ifq To: "BlueZ development" In-Reply-To: <1151516020.26495.10.camel@localhost> MIME-Version: 1.0 References: <1151479698.9544.1.camel@localhost> <1151516020.26495.10.camel@localhost> Subject: Re: [Bluez-devel] cross-compiling bluez-utils.3.1 Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1549437704==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net --===============1549437704== Content-Type: multipart/alternative; boundary="----=_Part_29435_17707867.1153282196807" ------=_Part_29435_17707867.1153282196807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline hello,marcel: I have a stupid question:can Bluez 3.1 run on ARM system? I cross-compiled the 3.1.and got lots of error. is there anyone have success cross-compile 3.1 to ARM?could you give me some advice? thanks very much. 2006/6/29, Marcel Holtmann : > > Hi Steve, > > > D-Bus seems like a useful tool for desktops, but possibly overkill > > and/or unnecessary for embedded systems. Also, as noted before, D-Bus > > will not build out of the box for cross-compiled systems such as ARM. > > Since a lot of embedded systems use Bluetooth, this seems problematic. > > I am aware of embedded systems and a long time this was the reason for > keeping D-Bus optional. In the long run it is not worth it and it would > only increase the complexity. Devices like the Nokia 770 proved that we > can handle D-Bus in the embedded area and if there are problems, they > must be addressed in D-Bus. > > > What exactly does D-Bus supply in terms of necessary/useful > functionality for > > Bluetooth, and how difficult would it be to work around having to use > it? (I > > have not taken a serious look at the new release yet, as I'm still > working > > on a basic understanding of the 2.21 version). > > D-Bus is a message bus (IPC based). Something like RPC and it makes > writing client applications a lot easier. The BlueZ D-Bus API provides a > clean interface to basic Bluetooth tasks. You don't need any knowledge > about HCI anymore. You can also write your application in C, C++, Java, > Python, C# etc. and they don't need to be put under GPL. > > Trying to implement your own message bus to avoid the D-Bus dependency > is not worth it. We considered it in the beginning, but this would > increase the complexity without any real benefit. > > Regards > > Marcel > > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bluez-devel mailing list > Bluez-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-devel > ------=_Part_29435_17707867.1153282196807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline hello,marcel:
I have a stupid question:can Bluez 3.1 run on ARM system?
I cross-compiled the 3.1.and got lots of error.
is there anyone have success cross-compile 3.1 to ARM?could you give me some advice?
thanks very much.

2006/6/29, Marcel Holtmann <marcel@holtmann.org>:

Hi Steve,

> D-Bus seems like a useful tool for desktops, but possibly overkill
> and/or unnecessary for embedded systems. Also, as noted before, D-Bus
> will not build out of the box for cross-compiled systems such as ARM.
> Since a lot of embedded systems use Bluetooth, this seems problematic.

I am aware of embedded systems and a long time this was the reason for
keeping D-Bus optional. In the long run it is not worth it and it would
only increase the complexity. Devices like the Nokia 770 proved that we
can handle D-Bus in the embedded area and if there are problems, they
must be addressed in D-Bus.

> What exactly does D-Bus supply in terms of necessary/useful functionality for
> Bluetooth, and how difficult would it be to work around having to use it? (I
> have not taken a serious look at the new release yet, as I'm still working
> on a basic understanding of the 2.21 version).

D-Bus is a message bus (IPC based). Something like RPC and it makes
writing client applications a lot easier. The BlueZ D-Bus API provides a
clean interface to basic Bluetooth tasks. You don't need any knowledge
about HCI anymore. You can also write your application in C, C++, Java,
Python, C# etc. and they don't need to be put under GPL.

Trying to implement your own message bus to avoid the D-Bus dependency
is not worth it. We considered it in the beginning, but this would
increase the complexity without any real benefit.

Regards

Marcel

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

------=_Part_29435_17707867.1153282196807-- --===============1549437704== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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 --===============1549437704== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============1549437704==--