On Wed, 2009-09-02 at 04:08 +0100, Chen, Congwu wrote:
>The changes necessary to fix this are a bit intrusive, but not
> * install libsyncevolution header files in a standard
> path: /usr/include/syncevolution/*.h
> * change the #include rules inside these .h files so that they use
> "syncevolution/" as prefix for all of them, rename
> directory to "syncevolution"
> * don't depend on config.h in the header files (apps might not
> have the same defines in their own config.h)
> * install libsyncevolution.la and add a .pc file for it
> * scan a directory for backends to open dynamically in
> SyncSource.cpp instead of using a hard-coded list
> (should also work when running inside the build directory, with backends in
I'm curious how can you implement this? How can we differentiate the situation
it is a production running or a running which is inside the build directory?
I can't think of any means of making that distinction either. We could
simply scan both the install dir *and* in addition src/backends/*/.libs,
all the time. The latter should take precedence.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.