On Tue, May 28, 2013 at 9:35 PM, DRC <dcomman...@users.sourceforge.net>wrote:
> There shouldn't be a "trunk" directory in your checkout. I think you
> may have checked out the code incorrectly from subversion. You should
> add "trunk" to the URL when you are checking it out. e.g.:
>
> svn co https://tigervnc.svn.sourceforge.net/svnroot/tigervnc/trunktigervnc
>
> I don't know that that will fix the build issue, but it might.
>
I don't think that was my issue - I knew to go for trunk
>
> The TigerVNC server build should pull in librfb.a, which depends on
> libjpeg-turbo. You can't successfully build the server without building
> the common directory first, which requires libjpeg-turbo.
>
Ah! I don't remember the build instructions mentioning the need to build
common first! That could well fix it for me.
>
> The server does not currently have a GUI for managing clients.
>
Ah right! Is this on the TODO list already?
>
> Best Android client: Well, there aren't a lot of these at the moment,
> and the ones that are there would not have TigerVNC's accelerated Tight
> decoding.
Hmm - that is a showstopper for me + TigerVNC then unfortunately as I was
mainly planning on accessing my server from Android (JB).
Since I posted I have got vnc4server compiled on my Pandaboard and its
working great from my PC - not tried it from Android yet as I'm waiting for
my BT keyboard/ touchpad to arrive.
> In the long term, we're working toward an Android version of
> TurboVNC that would perform optimally with a TigerVNC server as well.
> Currently, we have a Swing version in TurboVNC 1.2 that is based roughly
> on the TigerVNC 1.3 Java viewer but has numerous performance
> enhancements, including the ability to load libjpeg-turbo through JNI to
> achieve native levels of performance. However, since Swing isn't
> available on Android, the GUI parts of our viewer would have to be
> rewritten, or the back-end logic would have to be bolted onto an
> existing Android VNC viewer GUI, such as android-vnc-viewer. If any
> ambitious developers care to tackle that project, then I strongly
> encourage them to do so. I was originally working on the Android
> project for a customer, but they currently have demanding performance
> needs (3840 x 1200 @ 15 fps), and Android devices just aren't there yet.
> Thus, I've had to back burner it for now.
>
>
Thanks DRC and Dragseth for your help and advice on Android clients - those
were the two I was going to try first.
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Tigervnc-users mailing list
Tigervnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-users