aboutsummaryrefslogtreecommitdiffstats
path: root/common/rfb/encodings.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Remove unused rfb/util.h includesPierre Ossman2023-02-041-1/+0
| | | | | | | | These files don't use anything from this header, so remove the include. This exposes some missing includes in other places, though. So add an explicit include in the files that were relying on an indirect inclusion.
* H264 DecoderVladimir Sukhonosov2022-01-211-0/+6
| | | | Linux implementation using ffmpeg
* Be consistent in including config.hPierre Ossman2021-12-301-0/+5
| | | | | | The generally recommended way is to include it from source files, not headers. We had a mix of both. Let's try to be consistent and follow the recommended way.
* Remove a lot of platform compatibilty stuffPierre Ossman2014-07-071-3/+0
| | | | It's either not used, or no longer relevant.
* Eliminate GCC signed/unsigned warnings related to encodings: ThePeter Åstrand2010-02-101-1/+1
| | | | | | | | | | | | encoding in the RFB protocol has always been signed, and signed values are also used in the specification (ie DesktopName = -307 etc). In the code, however, unsigned types were used in a number of places, but not all, which causes warnings. This patch fixes the problem by switching to signed values everywhere. git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@3968 3789f03b-4d11-0410-bbf8-ca57d06f2519
* Migrating to new directory structure adopted from the RealVNC's source tree. ↵Constantin Kaplinsky2006-05-251-0/+49
More changes will follow. git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@589 3789f03b-4d11-0410-bbf8-ca57d06f2519