Patrick,
thanks for replying!

So here is what I see when I build "shared" ("statics" - I see only one desc of the module)

   Currently active::

    CalDAV
...
    TDE PIM Address Book = TDE PIM Contacts = addressbook = contacts = tdepim-contacts
...
    TDE PIM Address Book = TDE PIM Contacts = addressbook = contacts = tdepim-contacts
...
    TDE PIM Calendar = calendar = events = tdepim-events
...
    TDE PIM Task List = TDE Tasks = todo = tasks = tdepim-tasks
...
    TDE PIM Memos = memo = memos = tdepim-memos
...
    TDE PIM Calendar = calendar = events = tdepim-events
...
    TDE PIM Task List = TDE Tasks = todo = tasks = tdepim-tasks
...
    TDE PIM Memos = memo = memos = tdepim-memos
...

bin/syncevolution --version
SyncEvolution 1.5.1
Loading backend library /tmp/test/lib/syncevolution/backends/syncxmlrpc.so
Loading backend library /tmp/test/lib/syncevolution/backends/synctdepimcal.so  <<<< my cal module
Loading backend library /tmp/test/lib/syncevolution/backends/synctdepimabc.so <<<< my address book module
Loading backend library /tmp/test/lib/syncevolution/backends/syncsqlite.so
...
Loading backend library /tmp/test/lib/syncevolution/backends/syncdav.so
Loading backend library /tmp/test/lib/syncevolution/backends/syncakonadi.so
Loading backend library /tmp/test/lib/syncevolution/backends/syncactivesync.so
Loading backend library /tmp/test/lib/syncevolution/backends/providergoa.so
Loading backend library /tmp/test/lib/syncevolution/backends/platformkde.so
Loading backend library /tmp/test/lib/syncevolution/backends/platformgnome.so

Thanks


On Thursday, January 28, 2016 8:46 PM, Patrick Ohly <patrick.ohly@intel.com> wrote:


On Thu, 2016-01-28 at 17:56 +0000, Emanoil Kotsev wrote:
> Hi again,
>
> When I compile with --enable-shared my module comes up twice when I
> call --datastore-properties ?

Can you show the output?

Also check "syncevolution --version". It has some information about
loaded modules.



--
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.