Compiling tigervnc server on ubuntu armv7l

[redb...@gmail.com]

Hello,
I successfuly compiled tigervnc server, however I had to add DBUILD_VIEWER=OFF flag to cmake, because otherwise it was causing unresolved externals and I couldn't find a way to fix it.
However the main problem I have is different. After tigervnc compiled successfuly, I figured out that Xvnc binary is missing. Is it skipped in make scripts? How do I compile it?
I need the Xvnc that comes with tigervnc because from what I've heard it has xkeyboard extension built it and without this extension, I can't use applications using qtquick with vnc because there's no keyboard input. Please help!

[DRC]

Building Xvnc in TigerVNC isn't particularly easy, and I'm speaking as
the guy who used to generate the official binaries for this project
"back in the day." The most common way of doing it-- the method that
O/S distributors use-- involves building the server against pre-built
X11 SDKs and X.org source that match the running X server on the machine
on which you are building. But of course that produces a server that is
specific to that machine. Otherwise, to produce a cross-compatible
server, you have to build all of the X.org infrastructure from source
and then build the TigerVNC Server on top of it. I used to use the
build-xorg script in order to produce cross-compatible builds "back in
the day", but it's horribly outdated. I think Brian is now producing
cross-compatible builds using his own RPM and dpkg scripts that are
specific to a particular Red Hat or Ubuntu distribution (refer to
contrib/ in the source.) He would be the best person to tell you
whether the stuff under contrib/packages/deb will work on an ARM Ubuntu
distribution.

I should also point out, because we're one big VNC family here, that the
TurboVNC Server also supports XKEYBOARD and has a fully-contained Xvnc
source base. So if you run into a snag building the TigerVNC Server,
you may have better luck with ours, since it does do what you expect (it
builds Xvnc whenever you type "make".) The two servers should be mostly
compatible.

[Brian Hinz]

Have you tried using the ubuntu package sources in the contrib directory?  I was under the impression from issue #258 that they were confirmed to build & run on ubuntu arm platforms.

Can you please try following the instructions posted there (no need to patch anything if you're using the current git head) and let us know if it works for you?

Thanks,

-brian

[maksym....@noveltyrpas.com]

Thank you so much for your suggestion! It not only works 10x smoother and faster than tigervnc, but it also compiled without any bigger issues on tegra! (Not to mention it has support for OpenGL streaming which is simply AMAZING!). I have one final question though: It seems to work only with turbovnc client. Does it work with any other clients too?

PS
Unfortunately I still couldn't compile tigervnc and I gave up on it.

[DRC]

Our server should be fully compatible with the TigerVNC Viewer, and vice
versa, so you can mix and match. If that doesn't work for some reason,
then please file a bug on our GitHub page (github.com/turbovnc/turbovnc)
or contact me off-list. Both TigerVNC and TurboVNC support Turbo
encoding, which is a 100% compatible but highly optimized form of
TightVNC encoding, so any viewer should work, but when using viewers
other than TurboVNC or TigerVNC, the performance will be a lot slower
(TightVNC's viewers are compatible but not optimized, and other viewers
will cause the server to fall back to a slower and less efficient
encoding type, such as ZRLE or Hextile.)