[coldsync-hackers] plugins (dynamic library) and search paths.

[Fred Gylys-Colwell <fredgc@ktb.net>]

Hello,
I have been trying to write my own conduits and have two changes to coldsync
that I would find useful, and would be willing to contribute.

search paths:  I would like to have the .coldsyncrc file have a "search path"
so that I do not need to specify full path for each conduit.  The default path
would be the same place that the default plugins get installed.  Would anyone
else find this useful?  (I haven't actually done anything on this one yet.)

plugins:  I have added a routine that loads a library (using dlopen etc.) so
that I can recompile my plugin without re-installing coldsync.  It works under
linux, but I would need help getting it to compile on other platforms.  Should
I clean it up and post a patch?   To make it really clean, some of the data
structures in "coldsync.h" would have to be visible to the plugin, like in
include/pconn/something.h. 

Perhaps I have the wrong end of the stick on the second idea.  Can a conduit
talk to the palm directly?  I want to use high level routines like DlpOpenDB,
but that needs a PConnection.  It looks like only one PConnection is created at
the beginning, not one per conduit.  Are there any examples of Sync conduits
out there?

-- Fred GC.


-- 
----------------------------------------------------------------------
	    Fred Gylys-Colwell      fredgc@member.ams.org
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.