On Thu, 2008-05-08 at 18:08 +0100, Jonny Lamb wrote:
> Mark,
>
> I have just been preparing 0.11.1 Debian packages, and came across the
> changes to configure.ac.in in libsynce. I have gotten out of the loop
> on what's going down, so I'm not entirely sure what the changes are. The
> changes I refer to are in r3202 [0].
>
> Could you please outline what the difference between dccm-file-support,
> odccm-support, and hal-support is, please?
>
> Thanks very much,
>
> [0]
> http://synce.svn.sf.net/viewvc/synce/trunk/libsynce/configure.ac.in?r1=3018&r2=3202
>
Hi Jonny
Everything is enabled by default. In this state synce_info_new will look
for a device in a {v}dccm connection file first, then in odccm over
dbus, and finally a synce-hal connection.
The extra options are somewhat overkill, but
--enable-desktop-integration for odccm didn't seem appropriate anymore.
So libsynce can now be built with any combination of connection options.
odccm support requires libdbus, and hal support adds to this a
dependency on libhal.
I'd go for leaving it as the default, they all live happily together.
Hope this is what you need.
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
