Hi, first to introduce myself, I am 4 months into Linux (Debian Lenny), also
I have no computer qualification, so knowledge and experience are limited.
I have synce-kde 0.9.1.1.and, I think, all of the relevant apps available
via the sid repository. I am trying to install opensync for use with HP
ipaq, using http://www.synce.org/moin/SynceWithDebian
I am as far as:
"Unfortunately a few bits aren't packaged yet, so we'll need to compile
them.

sudo apt-get install subversion build-essential
**FIXME** Compile libwbxml here **FIXME**"

(This prompted me to search, which found your thread.)

I moved on to try compiling pywbxml- as follows:

svn co http://synce.svn.sf.net/svnroot/synce/trunk/pywbxml
cd pywbxml
./autogen.sh
make
sudo make install
cd ..

but result was:
"checking for WBXML2... configure: error: Package requirements (libwbxml2 >=
0.9.2) were not met:

No package 'libwbxml2' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables WBXML2_CFLAGS
and WBXML2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details."

However, libwbxml is readily available via apt. It's called libwbxml2.0,
version is 0.9.2.4 (sid repository). After installing this, I tried again
and had, in addition to above message:
Package libxml-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml-2.0.pc'
to the PKG_CONFIG_PATH environment variable.

(I regret I have been unable to find how to make the change suggested
above.)

I don't understand everything I'm reading, but if, as you say, sync-engine
is now libwbxml-free, do I need to persevere? I will be grateful for any
guidance.

I am of course happy to test and report as you ask.

Many thanks- Phil





Dr J A Gow wrote:
> 
> Folks,
> 
>       I've just committed the changes to make sync-engine libwbxml-free. I
> have tested this with the Opensync 0.3x stuff and it works well for
> contacts, tasks and events. At the moment I can't test with the Opensync
> 0.2x stuff as I don't have OS 0.2x installed on this box. Therefore it
> would be helpful if anyone with a bleeding-edge SynCE install and
> Opensync 0.2x who can sync, would test this and report problems.
> 
> I've left the debug spew in to help with this process - it will be easy
> to remove later.
> 
> The only problems you are likely to find is related to the fact that our
> implementation is now fussy about the correct namespaces being assigned
> to the libxml2 node structures - and sometimes this does not seem to
> work intuitively across the XSLT transform interface when extension
> functions create children. This will manifest itself as an exception
> being thrown when the wbxml code can't find the tag in the code page at
> the point of conversion. If you get one of these they are quite easy to
> fix so please just send me the dump from sync-engine (only the portion
> with the exception and, importantly, the XML document immediately before
> it) and I will sort it quickly.
> 
> Another point is that attribute support is badly broken in our wbxml
> implmentation. This does not matter for sync-engine as Airsync XML does
> not use attributes - but we should really sort this at some point for
> completeness and in case MS change something at a later date and
> suddenly decide to start using them!
> 
> Have fun.
> 
>       John.
> 
> 
> Excerpt from CHANGELOG:
> ----------------------
> 
>>From this point, sync-engine no longer relies on libwbxml and pywbxml.
> An internal wbxml converter has been implemented in  SyncEngine/wbxml
> (thanks to Jonny Lamb for the low level wbxml stuff). The user-facing
> API is unchanged.
> 
> Note that this has been tested successfully with the OS30 formats, but
> has NOT YET BEEN FULLY TESTED with Opensync 0.2x. The only problem that
> may be present here is incorrect namespace assignment within the
> converter code. Libwbxml parses it out from the strings whereas the
> internal implementation looks out for namespace assignments directly to
> the nodes in the libxml2 structures.
> 
> The implementation of this uncovered a couple of subtle errors in the
> general XML handling within sync-engine. These have been fixed, and the
> entire pathway will be checked when airsync.py is cleaned up shortly.
> 
> Attribute processing is badly broken in the wbxml implementation - this
> is not a problem for sync-engine as AirSync does not use attributes in
> its XML code. However this should be fixed up (can be as a low priority
> job) at some point for completeness and in case Microsoft go and change
> things at a later date.
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> SynCE-Devel mailing list
> SynCE-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/synce-devel
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Libwbxml-free-sync-engine-tp15214533p15299749.html
Sent from the iPAQ - SynCE - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel

Reply via email to