After approximately 35 hours of work in the past 3 days, I have a pre-release build and packaging system for TigerVNC up and running. The first run of packages from this can be found here:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases >From my point of view, the code is ready for beta. This work included a lot of cleanup in the Mac packaging system, the addition of automake targets for creating binary tarballs of both the TigerVNC Viewer and Server for Linux, various tweaks to accommodate custom GnuTLS builds, and a lot of testing. There are several issues I discovered in the process of testing, and I will make sure these get into the bug tracker. In the process of doing this, I also ran a new baseline benchmark study. Assuming encryption is turned off, TigerVNC has improved a bit since 1.0.1, probably largely due to the recent modification that enabled the use of the fast DCT when compressing images with JPEG quality < 96. It is still as much as 30% slower than TurboVNC, even though both are now using the same JPEG codec (results at the link below): http://www.virtualgl.org/About/TigerVNC In the course of this work, I've discovered much about how to build GnuTLS (and how not to.) I'm not sure how people are currently using that technology on Windows, but there doesn't seem to be a sane way to build static libraries for GnuTLS using Visual C++. Since shipping a binary that depends on the GnuTLS DLLs is equally problematic, what I did for now was to generate three different builds -- one using 32-bit MinGW that includes VeNCrypt support (but no WinVNC), as well as 32-bit and 64-bit builds using Visual C++, both of which include WinVNC (but no VeNCrypt.) At some point in the future, I hope that someone figures out a way to build the GnuTLS libraries using Visual C++. On a related note, Adam, do we still need to support autotools on Windows? We will still need to keep some of the Makefile.am files around, because they specify EXTRA_DIST, but we should remove the actual Windows automake code if it isn't needed anymore. CMake works fine with GnuTLS, as far as I can tell. Since all of this labor was unpaid, if anyone would like to donate to one of my other projects to help me offset the cost, it would be very much appreciated. The links for donations are under http://VirtualGL.org and http://libjpeg-turbo.VirtualGL.org. DRC ------------------------------------------------------------------------------ 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
