On Di, 2010-01-26 at 17:36 +0000, David Bremner wrote:
Currently it seems that having libopenobex in the build environment
not bluez causes syncevolution to fail to build.
See e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566940
following links to build logs, we see
checking for LIBSOUP... no
checking for LIBSOUP... yes
checking for LIBOPENOBEX... yes
checking for BLUEZ... no
checking for xsltproc... /usr/bin/xsltproc
checking for KEYRING... yes
checking for KEYRING_2_20... yes
I'm not sure if such a configuration makes sense for syncevolution;
I don't think it does.
not maybe the configure script could detect it and only enable libopenobex
if both libobex and bluez are found.
I agree. In addition, a configure option to enable or disable the
bluetooth support would be useful. Filed as:
FYI, I started a README.packagers today which happens to mention this:
Some of the advanced features of SyncEvolution depend on
packages. In addition to the more obvious dependencies of the
backends there are more subtle dependencies:
- for good time zone support, libsynthesis must have access to
either libical or libecal
- direct sync with phones depends on bluez and openobex
If there's additional information that should go into that file, please
let me know.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.