Hi,

Patrice Dumas wrote:

>My opinion is that the code associated with the static linking is hacky
>but clean. So it is fine, except that there is this circular dependency:
>libelektra needs backends (for the static filesys)
>backends needs libelektra (for kdbd) 
>  
>
In fact, all backends need elektra since they all use Key, KeySet struct
and their relative function. But, since these backend are dl_open() from
libelektra it seems symbol are correctly resolved at this time. But i don't
know if the constation that this works under Linux without add libelektra to
LIBADD's backends is a suffisant reason to not add it ... ?

About the static version there are several issue :
    * We shortcut libtool works providing our hand made stuff ;
       (and so we have to maintain uninteresting sutff like this
backend_symbols.c)
    * That need to compile twice most of source code ;

Iirc, the only problem which forced us to act like that is we don't know
the real name of libelektra-default. Libltdl have great stuff for manage
shared or static version totally transparently, but "default" backend isn't
a real backend. Searching symbol "kdbBackendFactory" from
"libelektra-default"
using libltdl simply fail cause of that (libltdl search for
"libelektra_default_LTX_kdbBackendFactory"
symbol). If we are able to know the true name of default backend,
this would be no more a problem.

This is the time where the configuration framework need configuration ;-)

Regards,
Yannick.





-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list

Reply via email to