Lines Matching refs:dbus

5 Fedora: dbus-devel
12 $ cmake .. -DLWS_ROLE_DBUS=1 -DLWS_DBUS_INCLUDE2="/usr/lib64/dbus-1.0/include"
17 $ cmake .. -DLWS_ROLE_DBUS=1 -DLWS_DBUS_INCLUDE2="/usr/lib/x86_64-linux-gnu/dbus-1.0/include"
26 `/usr/include/dbus-1.0`... if the directory exists, it is used.
28 For `LWS_DBUS_INCLUDE2`, it is the arch-specific dbus header which may be
29 packaged separately than the main dbus headers.  On Fedora, this is in
30 `/usr/lib[64]/dbus-1.0/include`... if not given externally, lws cmake will
31 try `/usr/lib64/dbus-1.0/include`.  On Debian / Ubuntu, the package installs
32 it in an arch-specific dir like `/usr/lib/x86_64-linux-gnu/dbus-1.0/include`,
35 The library path is usually \[lib\] "dbus-1", but this can also be forced if
38 ## Building against local dbus build
40 If you built your own local dbus and installed it in /usr/local, then
41 this is the incantation to direct lws to use the local version of dbus:
44 …OLE_DBUS=1 -DLWS_DBUS_INCLUDE1="/usr/local/include/dbus-1.0" -DLWS_DBUS_INCLUDE2="/usr/local/lib/d…
48 there's a perfectly good dbus lib already in `/usr/lib[64]` using `LD_PRELOAD`
55 ## Lws dbus api exports
58 dbus helpers, which use dbus types, as usual from `#include <libwebsockets.h>`
59 then if lws was compiled with dbus role support it forces all users to take
60 care about the dbus include path mess whether they use dbus themselves or not.
62 For that reason, if you need access to the lws dbus apis, you must explicitly
66 #include <libwebsockets/lws-dbus.h>
69 This includes `<dbus/dbus.h>` and so requires the include paths set up.  But
70 otherwise non-dbus users that don't include `libwebsockets/lws-dbus.h` don't
75 https://cgit.freedesktop.org/dbus/dbus/tree/README.valgrind