On Fri, Feb 11, 2011 at 02:22:04PM -0600, DRC wrote: > Well, yes and no. libssh requires OpenSSL, right? That means we have > to statically link with OpenSSL in order to produce cross-compatible > binaries. Static linking with OpenSSL is, I can tell you from > experience, not my favorite pastime. And now, if someone wants to build > a full-featured version of TigerVNC, they need OpenSSL, libssh, GnuTLS, > libgcrypt, libgpg-error, libtasn1. Yuck. I really want us to reduce > some of the existing complexity before we start adding more.
Isn't OpenSSL released under a GPL incompatible license? Regards, Martin Kögler ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
