On Wed, 2009-12-16 at 02:06 +0000, Dr J A Gow wrote: > On Mon, 2009-12-14 at 22:32 +0000, Mark Ellis wrote: > > > Ditto on the innards :) > > > > Managed to get trunk, and regenerated the patch to build against it. Not > > much success with testing however, due to some apparently dodgy code in > > the opensync python wrapper, with C style comments and other whatnot. I > > know absolutely nothing about swig ... > > > > Just went to sort out another machine with a fresh build of Opensync to > try this: would you believe it looks like Opensync have managed to break > the evo2 plugin in trunk! It just hangs (definitely the evo plugin is > the problem, file-sync works ok). > > Anybody else seen this? If so I'll report it on the Opensync bugtracker. >
To add to my above, I really don't know what the Opensync people are doing with their trunk at the moment - nothing seems to work properly. Evo2, xslt-format, python-module either won't build or are broken at run-time. I can get 0.39 to build and run, but I am really not sure whether to push forward with 0.39 to fix up the sync-engine conversions, or to just wait until the opensync svn tree is a bit more stable before making the changes. Chances are Opensync will change something and I will still be chasing a moving target..... Grrrrr! John. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
