You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
message(WARNING"*** The libjpeg library you are building against is not libjpeg-turbo. Performance will be reduced. You can obtain libjpeg-turbo from: https://sourceforge.net/projects/libjpeg-turbo/files/ ***")
136
+
else()
137
+
message(STATUS"Detected libjpeg-turbo via ${JPEGLIB_H_PATH}")
Copy file name to clipboardExpand all lines: README.md
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,8 @@
5
5
LibVNCServer: A library for easy implementation of a VNC server.
6
6
Copyright (C) 2001-2003 Johannes E. Schindelin
7
7
8
+
If you have a general question, it's best to [ask in the community chat](https://gitter.im/LibVNC/libvncserver). If your concern is about a bug or feature request instead, please use [the issue tracker](https://github.com/LibVNC/libvncserver/issues).
9
+
8
10
If you already used LibVNCServer, you probably want to read [NEWS](NEWS.md).
9
11
10
12
What is it?
@@ -53,7 +55,6 @@ RFB Protocol Support Status
53
55
| Hextile | 5 | ✔ | ✔ |
54
56
| Zlib | 6 | ✔ | ✔ |
55
57
| Tight | 7 | ✔ | ✔ |
56
-
| Zlibhex | 8 | ✔ ||
57
58
| Ultra | 9 | ✔ | ✔ |
58
59
| TRLE | 15 || ✔ |
59
60
| ZRLE | 16 | ✔ | ✔ |
@@ -123,7 +124,9 @@ Tested with MinGW-w64 on Debian, which you should install via `sudo apt install
123
124
You can make use of the [provided toolchainfile](cmake/Toolchain-cross-mingw32-linux.cmake).
124
125
It sets CMake to expect (optional) win32 dependencies like libjpeg and friends
125
126
in the `deps` directory. Note that you need (probably self-built) development packages for
126
-
win32, the `-dev` packages coming with your distribution won't work.
127
+
win32, the `-dev` packages coming with your distribution won't work. Also note that you'll
128
+
need to put `libwinpthread-1.dll` in the build dir to run the examples. You can find this DLL
129
+
on your Linux build machine via `locate libwinpthread-1.dll`.
127
130
128
131
129
132
mkdir build
@@ -228,10 +231,10 @@ high latency or both.
228
231
229
232
On a high-latency link, try asking for framebuffer updates continously, as
230
233
RFB is client-pull per default, not server-push. One example implementation
231
-
can be found [here](https://github.com/bk138/multivnc/blob/master/src/VNCConn.cpp#L1112)
234
+
can be found [here](https://github.com/bk138/multivnc/blob/6251169ed11835ed709c0c191599937759856dda/src/VNCConn.cpp#L1112)
232
235
and it definitely improves responsiveness.
233
236
234
-
There also is the [ContinuousUpdates RFB extension](https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#continuousupdates-pseudo-encoding),
237
+
There also is the [ContinuousUpdates RFB extension](https://github.com/rfbproto/rfbproto/blob/513c651fff1b213188daa5069444145a63e71617/rfbproto.rst#L4052),
235
238
but that one is not supported by LibVNC (yet).
236
239
237
240
### Tackling Low Throughput
@@ -250,7 +253,7 @@ bytes that get sent per framebuffer update:
250
253
* Send a scaled-down version of your framebuffer. You can do the scaling in your
251
254
application feeding data into LibVNCServer's framebuffer (would affect all clients)
252
255
or let LibVNCServer do the work for you if your client requests a scaled screen
253
-
via a [SetScale or SetScaleFactor message](https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#74client-to-server-messages)
256
+
via a [SetScale or SetScaleFactor message](https://github.com/rfbproto/rfbproto/blob/513c651fff1b213188daa5069444145a63e71617/rfbproto.rst#L1344)
254
257
(this is per-client scaling - UltraVNC viewers can request this).
0 commit comments