http://bugzilla.moblin.org/show_bug.cgi?id=6181
--- Comment #1 from Chen Congwu <[email protected]> 2009-09-16 23:40:39 --- >> >We can keep the config.h usage and the ifdefs in our header files. We >> >just have to be careful that we include config.h like this >> > #ifdef HAVE_CONFIG_H >> > # include <config.h> >> > #endif >> >and that none of the ifdefs affect structs that are part of the API. >> > >> >For example, in EvolutionSmartPtr.h, "#ifdef HAVE_GLIB" only adds some >> >declarations. The header file can be used just fine by a client program >> >without those if it doesn't provide a config.h or doesn't use GLib >> >itself. >> Yes, but I will first try to split some non-api stuff to another >> library (EvolutionSyncClient, Transport Implemenation) Maybe not get your idea, but: Is it a potential problem, if we built libsyncevolution with no glib; while the library user defines HAVA_GLIB and indeed have glib library. So the library developers built the library with a set of assumptions, and the library user can use the library with another set of assumptions, is it workable? > We have discussed how to scan possible backend libraries both from a > standard > path > and the built directory; Patrick pointed out a possible solution to scan the > > program path > which is passed in as argv[0] in main. This still not worked easily because > we are relying > on the static initialization which is before the main routine is called. We > may need to > clean up the static initializations if possible. I now add a configuration option: enable-maintainence-mode, when with it we will just scan backends/**/.libs/*.so otherwise we will stick to $prefix/libsyncevolution/backends/*.so -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
