On Fri, 2012-01-13 at 17:09 +0100, Patrick Ohly wrote: > On Do, 2012-01-05 at 16:55 +0100, Murray Cumming wrote: > > As far as I can tell, this patch should be applied. Or is there some > > reason to compile the code in dbus/ if --enable-dbus-service is not > > used? > > For a while I compiled sync-ui and core SyncEvolution separately in > MeeGo. In that case, D-Bus service is disabled and dbus/glib needs to be > compiled. > > In other words, decoupling dbus compilation from D-Bus service > compilation makes sense. But probably some of the current checks for > what needs to be compiled inside dbus are not quite correct, because > there is no real "enable/disable D-Bus" switch in configure.
I don't really understand. What is the dbus/ code used for if no dbus-service is built or used? We also noticed a relinking problem during make install, which is fixed by this commit: https://meego.gitorious.org/~krnowak/meego-middleware/krnowaks-syncevolution/commit/d4282ec7e920136c6ad92f82f908e6698178b014 It's already in the concurrent-sync-sessions branch, though this URL will probably stop working after a future rebase: http://meego.gitorious.org/meego-middleware/syncevolution/commit/cac0725b2f30dcb3f739b3989b3a67ce7a695273 I suggest that you put this in master. This is necessary because you install some libraries in <prefix>/lib/syncevolution/ but other libraries in <prefix>/lib/ and autotools is apparently not able to deal with that when relinking before installing. Is there a good reason for installing some libraries in a sub-directory. Simplifying that might let use remove some hacks from the build files. -- Murray Cumming [email protected] www.murrayc.com www.openismus.com _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
