All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] bluez
Date: Thu, 6 Nov 2008 17:43:40 +0100	[thread overview]
Message-ID: <20081106174340.208dc156@surf> (raw)
In-Reply-To: <c88e466f0811060612r70f1d4f7nec4376aca9414dbe@mail.gmail.com>

Le Thu, 6 Nov 2008 15:12:02 +0100,
"Michel Benoit" <michel.benoit@sepab.se> a ?crit :

> Has anyone cross compiled bluez-libs and bluez-utils with buildroot?

As far as I can see, we don't have these packages in Buildroot yet, and
there doesn't seem to be anything related to bluez in the bug tracker
(but the search engine looks a bit weird, no sure it works properly).

Back in 2005, some people tried to compile bluez with Buildroot, see
http://osdir.com/ml/bluez.devel/2005-03/msg00089.html.

Anyway, adding support for bluez-libs and bluez-utils to buildroot
should be relatively simple, since they use the classical autotools. A
few lines of .mk and Config.in should do the basic things.

Do you want to provide a patch for these ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2008-11-06 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 14:12 [Buildroot] bluez Michel Benoit
2008-11-06 16:43 ` Thomas Petazzoni [this message]
2008-11-07 11:06   ` Julien Boibessot
2008-11-07 11:16     ` Nick.Thompson at infineon.com
2008-11-10 14:56       ` Matuschka, Sebastian
2008-11-10 15:10         ` Nick.Thompson at infineon.com
2008-11-13 10:09         ` Nick.Thompson at infineon.com
2009-06-28 17:31           ` Julien Boibessot

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=20081106174340.208dc156@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.