On Wed, 2012-09-05 at 11:30 +0200, Andrzej J. R. Hunt wrote:
On 09/04/2012 05:47 PM, Caolán McNamara wrote:
1. Port my code to dbus-glib and always build dbus-glib? Or port my
code to dbus-glib and leave everything else as is, meaning bluetooth
on Linux needs the user to use --enable-dbus?
I feel this is the best approach. Except that I'll toggle enable-dbus on
by default rather than off when I get the chance.
done with 4573b628cc1d18bb623a1f64b35ee6e113dcf03f now
I don't think it's too critical to have dbus enabled, but would be
nice to have for 3.7.
Yeah, we should sort out whether anyone's got the time to raise the
baseline that we use for the universal build.
Would it not be more appropriate to use g_debug rather than g_warning
for these messages
True, they shouldn't really be warnings, it no biggy if the services
don't exist. Done now as e053f8cb0fc78bae274b74d7fed59d211e5c9f26
C.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.