-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,
currently libclamav is used in a "static" way while
compiled as shared, I mean that all internal
functions are in the .so and binary that links
that are using them from the .so
cli_x functions should be internals and the executables
should link only the cl_xxx
On unix this is not really a problem since the linker
is smarter than the win32 linker
In my win32 port I had to export symbols that are currently
named as internals
as in:
http://clamwin.svn.sourceforge.net/viewvc/clamwin/trunk/clamav-devel/contrib/msvc/libclamav.def?revision=1537&view=markup

there are currently some of cli_ symbols exported
and other ones that I avoided by linking directly .c in the single
executables

for this reason libclamunrar introduces circular dependancies
and it's not buildable as is in win32 and standalone
on unix
(perhaps easy solvable since it uses snprintf that is public domain
and not gpl and other symbols are cli_malloc and cli_readn and friends)

I think that is not really easy right now to avoid
exporting internal functions because of the breakage of
package executables compilation, but
for external apps that are linking libclamav it would be nice
to restrict the usage to clamav.h defined symbols

Regards

- --
Gianluigi Tiesi <[EMAIL PROTECTED]>
EDP Project Leader
Netfarm S.r.l. - http://www.netfarm.it/
Free Software: http://oss.netfarm.it/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQ0Tc3UE5cRfnO04RAvi6AJ9hlROxzvNZQyZVxdABewYgMhArngCguHCI
xRdyFEXwKE9vGB5ofDr5bks=
=eAFh
-----END PGP SIGNATURE-----
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net

Reply via email to