Gianluca Sforna wrote:
The topic of removing OpenSSL from the codebase was raised several
times in the past.
Let me sum up the reasoning (and correct me where I'm wrong)
1. the license is incompatible with the GPL
This could be worked around with an exception to the OW license
We can change the license by adding:
"As a special exception, Wengo gives permission to link this program
with the OpenSSL Library." It was done this way for classic
2. libgaim already pulls in a dependency from gnuTLS
that is, we have 2 different libraries linked for the same purpose
3. OpenSSH is used by owcurl (which, BTW, I would _really_ like to see
disappearing as well)
this means we need to replace openSSL with something compatible with it
So, the natural choice would be gnuTLS, but it seems that it can not
build on Windows (I am not sure if the build was actually tried, and
with which compiler)
Exactly gnuTLS under Windows is a really big unknown.
For example under Windows GAIM does not use gnuTLS but the stuffs from
Netscape (that are obsolete by the way).
One thing is sure: supporting OpenSSL under Windows + gnuTLS under Linux
is quite complex and time consuming.
About the new cmake system, there are still some work to do on it. I
hope to finish an experimental Windows support soon (for the moment it
fails linking qtwengophone but everything else works) + it needs some
cleanup.
yaSSL seems to be really nice, thx for the link! libcurl support +
OpenSSL compatibility layer + Multiple OS support seems to be perfect!
--
Tanguy Krotoff <[EMAIL PROTECTED]>
http://openwengo.org
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
