Hey all, I've had a brief look at building syncevolution for the mac. It looks like it is going to be more work than I thought. Libsynthesis itself doesn't build on a mac (there are some linker options that it has hard wired in src/Makefile.am that aren't supported by ld on the mac, specifically "--version-script", and disabling shared libraries fails in other ways). I then started looking at what I was trying to do a little more. I want my Mac to Sync with my Android phone. I don't really want an external server, which is why I was somewhat interested in your direct synchronisation plans: <http://moblin.org/documentation/syncevolution/direct-synchronization-aka-... But that then starts to look very like Apple's iSync setup. They have what appears to have started life as something like SyncML server. It never reached full SyncML server status, but it does do many similar things. For example, it synchronises nicely with SyncML phones over OBEX (I used this before I got my android phone). iSync supports plugins that look vaguely similar to 'sever stubs' mentioned in the moblin document above. They seems to do some extra processing though in that they can map from Apple's internal representation back down into simpler representations for phones (which sounds vaguely similar to what is described here: <http://www.estamos.de/blog/2008/07/07/syncml-mac-os-x/ <http://developer.apple.com/mac/library/documentation/Syncing/Conceptual/T... but if you actually play with the plugin-maker (it is part of the MacOS Developer Tools available on Apple's website), it is pretty clear that it is designed to make iSync talk to OBEX enabled SyncML clients with different capabilities. Interestingly, in the Advanced Options, it is possible to select "HTTP Server" as the SyncML Bearer (rather than "Obex Server" or the default, "Obex Client"). I haven't found out how to use this yet. At this stage I'm considering my options - none of them look simple. Cheers, Will :-}