Not really a TigerVNC problem then, but perhaps a problem with some of
the recommended patches. Does it work if you omit them? In that case, it
should be fairly easy to figure out which patch is causing the problem
by bisecting.
It is a TigerVNC problem, because I was following the exact procedure that
you guys added to BUILDING.txt for building FLTK,
We could perhaps clarify that those patches are not strictly necessary. It
should always be possible to build TigerVNC even without them, but with
somewhat limited functionality. If such a build fails, please report.
Also, it seems the problem was with linking Fluid. Since TigerVNC does not
depend on Fluid, one solution could be to just comment out the Fluid build
from the FLTK makefile.
Another good thing is that many of our patches are being accepted by the
FLTK project, some of them even into the 1.3 branch. With the latest FLTK
snapshot, fewer patches should be required even for full functionality,
but we haven't been able to verify this yet. Hopefully, FLTK will also
release a 1.3.1 version soon.
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://cendio.com
Teknikringen 8 http://twitter.com/ThinLinc
583 30 Linköping http://facebook.com/ThinLinc
Phone: +46-13-214600 http://plus.google.com/112509906846170010689
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users
