On Thu, 2010-06-24 at 22:45 +0100, h2oz7v wrote:
> On Thu, Jun 24, 2010 at 8:42 PM, Patrick Ohly <[email protected]> wrote:
> > Yes. The configure script defaults to building with Evolution and
> > complains if the development files are not found, but using
> > --disable-ebook --disable-ecal will tell it to proceed anyway.
>
> Thanks. I'm getting somewhere with the compilation, though have
> reached an error. Attached is the build log.
>
> So far, I have installed the following dependencies:
>
> * openobex
> * bluez
>
> makedepends:
>
> * autoconf
> * boost
> * pkgconfig
>
> ... referring to this page on the wiki:
>
> http://syncevolution.org/wiki/packaging-syncevolution
>
> Have I missed any?
No, you found a bug in the configure scripts. You compile the
SoupTransportAgent, which happens to depend on glib-dev, but that isn't
enabled in the configure script. I can reproduce the failure and have a
fix.
You can fix this in two ways:
1. use --enable-dbus-service - this happens to pull in glib; you'll
need that anyway if you want to synchronize TB directly with
SyncEvolution, the syncevo-http-server depends on it
2. apply the attached patch
> > I don't quite see how SyncEvolution gets involved here. Do you mean that
> > you'll sync TB<->Funambol<->SyncEvolution<->phone? That's possible, but
> > wouldn't it be easier to sync Funambol and the phone directly?
>
> It probably would be except Funambol doesn't support SyncML OBEX over
> Bluetooth directly (it uses HTTP bindings).
In other words, you run the Funambol server locally and can access it
with TB and SyncEvolution, but not the phone. In that case a local sync
with SyncEvolution as server may be the simpler setup.
See http://syncevolution.org/development/http-server-howto
> > Or use SyncEvolution as local SyncML server and sync
> > TB<->SyncEvolution<->phone.
> >
> > In both case you can use the local file backend in SyncEvolution to
> > store data.
>
> That would be more of an ideal approach. I'll read up about the local
> file backend.
The HOWTO mentioned above shows how to set it up.
> First step is to get syncEvo installed :)
Note that you can install the binaries from syncevolution.org, if one of
them fits your platform. They contain the Evolution backend, but will
install and run fine without Evolution installed.
--
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.
diff --git a/configure-pre.in b/configure-pre.in
index 08f9ee3..e32c370 100644
--- a/configure-pre.in
+++ b/configure-pre.in
@@ -221,6 +221,9 @@ AC_ARG_ENABLE(libsoup,
AC_DEFINE(ENABLE_LIBSOUP, 1, [enable libsoup transport])
fi ])
+# SoupTransportAgent depends on glib
+case "$TRANSPORT" in *libsoup*) need_glib=yes;; esac
+
bluetooth_disabled=no
AC_ARG_ENABLE(bluetooth,
AC_HELP_STRING([--enable-bluetooth],
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
