On Thu, 23.10.14 07:06, Filipe Brandenburger (filbran...@google.com) wrote:
Hi Lennart,
On Wed, Oct 22, 2014 at 2:07 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Mon, 25.08.14 21:58, Filipe Brandenburger (filbran...@google.com) wrote:
Indeed it would be good to clarify that
On 23/10/14 12:21, Lennart Poettering wrote:
The behaviour should really be to:
1. take the paths from configure switches
2. if they are not specified, try to get them from pkg-config
3. if the relevant pkg-config files are not installed, generate an error and
refuse build
Actually...
On Thu, 23.10.14 12:44, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
On 23/10/14 12:21, Lennart Poettering wrote:
The behaviour should really be to:
1. take the paths from configure switches
2. if they are not specified, try to get them from pkg-config
3. if the relevant
On Mon, 25.08.14 21:58, Filipe Brandenburger (filbran...@google.com) wrote:
On Wed, Aug 20, 2014 at 3:27 PM, Lennart Poettering
lenn...@poettering.net wrote:
Well, we have our own dbus library implementation since a while
(sd-bus) that supports both dbus1 and kdbus as transport. We only
On Wed, 20.08.14 11:45, Filipe Brandenburger (filbran...@google.com) wrote:
Hi,
I'm wondering about systemd's build dependency on dbus... I see that
the configure script checks for dbus, but the exported variables are
rarely used.
For instance, HAVE_DBUS is defined but only used in test