linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@profusion.mobi>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ v3 1/5] build-sys: Don't build gdbus several times
Date: Tue, 25 Jun 2013 15:50:00 -0300	[thread overview]
Message-ID: <CAMOw1v6rsJA2R3xcTYjaRYsOX6N2jPhvTskVmn+ugqxUbLpgAg@mail.gmail.com> (raw)
In-Reply-To: <EF5E15A5-5F57-458F-8E6E-8B0850958E9A@holtmann.org>

On Fri, Jun 21, 2013 at 7:47 PM, Marcel Holtmann <marcel@holtmann.org> wrot=
e:
> Hi Lucas,
>
>>>> We are currently compiling gdbus 3 times: one for tests, one for
>>>> bluetoothd and another for obexd.
>>>
>>> we recompile because of the different CFLAGS for these binaries.
>>
>> But they shouldn=B4t be affecting gdbus.
>>
>>>
>>>> $ ls gdbus/*watch.o
>>>> gdbus/bluetoothd-watch.o  gdbus/obexd-watch.o  gdbus/watch.o
>>>>
>>>> Instead of prepending $(gdbus_sources) to several _SOURCES variable, u=
se
>>>> a convenience library.
>>>
>>> When we switched to non-recursive build, we stopped building interim li=
braries. What is the benefit of going back to building them. I am personall=
y fine with building gdbus several times.
>>
>> It=B4s more that there=B4s no advantage doing otherwise. The small benef=
it
>> is building less files and letting it simpler.
>
> then at least get into a bit of a standard habit. We are building libblue=
tooth into a public and private version.
>
> Currently we name it libbluetooth-private, but maybe following the system=
d "standard", we should start calling that libbluetooth-internal. And then =
libgdbus-internal.

ok

>
> You also do realize that I will make you do this for all other projects u=
sing gdbus.

hahaha... ok

Lucas De Marchi

      reply	other threads:[~2013-06-25 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 14:17 [PATCH BlueZ v3 1/5] build-sys: Don't build gdbus several times Lucas De Marchi
2013-06-21 14:17 ` [PATCH BlueZ v3 2/5] gitignore: Add missing tools Lucas De Marchi
2013-06-21 14:17 ` [PATCH BlueZ v3 3/5] adapter: Remove never used parameter Lucas De Marchi
2013-06-21 14:17 ` [PATCH BlueZ v3 4/5] client: Add description for default-agent command Lucas De Marchi
2013-06-21 14:17 ` [PATCH BlueZ v3 5/5] client: prettify help table Lucas De Marchi
2013-06-24  8:14   ` Johan Hedberg
2013-06-21 22:02 ` [PATCH BlueZ v3 1/5] build-sys: Don't build gdbus several times Marcel Holtmann
2013-06-21 22:37   ` Lucas De Marchi
2013-06-21 22:47     ` Marcel Holtmann
2013-06-25 18:50       ` Lucas De Marchi [this message]

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=CAMOw1v6rsJA2R3xcTYjaRYsOX6N2jPhvTskVmn+ugqxUbLpgAg@mail.gmail.com \
    --to=lucas.demarchi@profusion.mobi \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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;
as well as URLs for NNTP newsgroup(s).