Long time no see... :-) Checked the mail and found a nice patch, kindly provided by Alexander Logvinov with the code required to automatically disable multi-threaded operations with libfuse (which had to be manually done on the 0.4.4 version, with the recent versions of synce).
Alexander also reported that FUR is FreeBSD compatible. Seems like i created a FreeBSD compatible code without ever having installed one. Geez... I'm good! xD
Starting from the release 0.4.5 the -s flag will not be necessary anymore! Thank you Alexander!
The problem of the compatibility between FUR and the new version of the librapi (0.12) seem to root in the multi thread access that FUR does, through fuse, to the synce functions.
The new version of librapi seems to be less tolerant than the older one for multi thread access: a quick fix to this problem is to run Fur with the -s option, disabling the thread enabled main loop in fuse in favour of a serial one.
I have verified that the current version of FUR (as well as the 0.4.3) doesn't seem to be compatible with the newer version of librapi (0.12), at least on the HTC Excalibur. I will investigate the issue.
People interested in using FUR and with an older and working version of the synce libraries are encouraged to stick to it, at least until the issue will be sorted. Thank you for your patience.
This release also (un)implement some changes that i slipped without notice in the 0.4.3 release: namely the truncate call, which caused a lot of problems with the new librapi releases which doesn't implement it, has been removed.
I have run the last version (0.4.3, patch entirely contributed by Matthias Gruenewald) from the first time and it worked fine (with the notable exception of the proc tree which never worked properly, since it's implementation, on WM5-WM6 devices) however during the compilation i have noticed that the function CESetEndOfFile has been disabled in the SVN: this means that if you want to compile FUR, you'll have to use the freshmeat synce packages (0.10.0) or (if you want to compile the Synce packages) the source packages (not the SVN).
Hard core programmers may of course simply use the svn source and remove the appropriate '#if 0/#endif' lines from the librapi2 package in order to re-enable the API again. At their own risk, of course :-)
Thank to northx im working on FUR again and i've noticed how unclear my site is (If 90% of people that read my site cannot find the informations they need to compile and install maybe it's my fault :-) ).
Therefore im reorganizing my site, removing the obsolete informations and adding the latest news in the proper sections: i don't like to write documentation very much, but i have vowed not to let the "Latest News" section grow too much without integrating the infos in the site.
The old FUR page will be available here as everlasting testament of my laziness.
I browsed the Synce Project page and it seems the developers did a lot of work since the last time i checked (Thank you!), some of which will directly benefit FUR once i will have done the homework; the same can be said about Fuse: FUR uses it through the API version 22 though the current is 26.
At the moment I'm not much interested in FUR anymore: mostly because i don't connect winCE based devices to my computer anymore (and when i do, to just move data, i find FUR overkill and slow when compared with a SSD card reader), however i keep mantaining the project by applying third party patches and trying to fix bugs when they are reported, if I'm able to.
Please be patient if i don't answer to your email immediately: as far as i know, everyone that contacted me about FUR always got an answer eventually (mean wait time ranges from 1 day to a week, depending on various factors, including spam...). Thank you all for your patience and contributions.
Next |
|