If you first unload openssl and then terminate xmlsec then it explains it. You should kill xmlsec first andMay be the problem lies on the fact that our application loaded openssl lib before initializing xmlseclib and terminate it itself.
*next* openssl.
Yes, I know. I defined WITH_DL= 0 and and it works well :-)Yes, it was the case because dynamic crypto loading *was not* implemented for windows at that moment :)
But http://www.aleksey.com/pipermail/xmlsec/2003/001391.html claims that
build on Windows
defaultly doesn't support dynamic loading.
Aleksey
_______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
