From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Patch: inheritance problem in gsta2dpsink
Date: Mon, 8 Oct 2007 19:32:52 -0600 [thread overview]
Message-ID: <d89ddf300710081832w1ac37dfana49571dc9306dbf2@mail.gmail.com> (raw)
In-Reply-To: <1191884194.12212.13.camel@aeonflux.holtmann.net>
Hey
I asked Marcel the same thing a while back.
It would make sense to factor the common stuff into unix.c or create
an ipc.c for that. We can link these to each plugin without messing
around with libraries.
Brad
On 10/8/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Luiz,
>
> > I guess we really need a tiny library for ipc, we dont want to
> > duplicate code from
> > pcm_bluetooth.c again in a2dpsink, it might happen that someone need this
> > in another plugin or so.
>
> no no and no. I don't care what other plugins (outside bluez-utils) need
> and want at the moment. It is perfectly fine to link an object file more
> than once. That must be enough and a library in the end is nothing
> different.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-09 1:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 21:31 [Bluez-devel] Patch: inheritance problem in gsta2dpsink thiagoss
2007-10-05 19:36 ` thiagoss
2007-10-08 17:56 ` Luiz Augusto von Dentz
2007-10-08 22:56 ` Marcel Holtmann
2007-10-09 1:32 ` Brad Midgley [this message]
2007-10-09 8:01 ` Fabien Chevalier
2007-10-09 8:44 ` Marcel Holtmann
2007-10-09 10:01 ` Fabien Chevalier
2007-10-09 21:17 ` Luiz Augusto von Dentz
2007-10-10 0:51 ` Marcel Holtmann
2007-10-10 13:31 ` Luiz Augusto von Dentz
2007-10-10 14: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=d89ddf300710081832w1ac37dfana49571dc9306dbf2@mail.gmail.com \
--to=bmidgley@gmail.com \
--cc=bluez-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox