| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Constructors that do a lot of work and can fail under normal usage is
confusing and difficult to work with. Move the connection stage to an
explicit method instead.
|
|
|
|
|
|
| |
If we fail to connect, then socket object will never be created.
Bug fix for 22dd29 and c2f5cfe.
|
|\ |
|
| |
| |
| |
| | |
To give users and packagers more control.
|
| |
| |
| |
| | |
Just like the other options we have that rely on external components.
|
| |
| |
| |
| | |
So we use the standard method to find libraries.
|
| |
| |
| |
| | |
So we use the standard method to find libraries.
|
| |
| |
| |
| | |
So we use the standard method to find libraries.
|
| |
| |
| |
| | |
So we use the standard method to find libraries.
|
| |
| |
| |
| | |
CMake now includes a module for this, so avoid doing it ourselves.
|
| |
| |
| |
| | |
MSYS2 now packages a static version of this library.
|
| |
| |
| |
| | |
We don't use pkg-config to find gettext, so these are not set.
|
| |
| |
| |
| |
| | |
These are the core libraries for gettext, so no need to check if they
exist or not.
|
| |
| |
| |
| | |
These are misleading and likely out of date.
|
| |
| |
| |
| |
| | |
Follow what CMake's own find modules do to get a consistent and
understandable behaviour.
|
| |
| |
| |
| |
| |
| | |
These headers are supposed to include that directory in the #include
statements. Only reason this "worked" so far was because we always
managed to rely on the pkg-config information rather than find_path().
|
| |
| |
| |
| | |
It's not something users of the find module should need to deal with.
|
| |
| |
| |
| |
| | |
FFmpeg is a suite of independent libraries, and is often split up when
packaged. Split our find modules the same way for clarity.
|
| |
| |
| |
| | |
Follow the naming convention that the upstream project uses.
|
|/
|
|
| |
Follow the same style that CMake itself uses.
|
| |
|
|
|
|
| |
Avoid error prone manual memory management and string handling.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Fixes: https://issues.redhat.com/browse/RHEL-34880
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| |
| | |
Send the generic "Authentication failed" if the PAM module does not pass
an error message.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| | |
It is not used anywhere else.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Return zero if the current argument starts with ":". It's useless to
check if it matches any of the other Xvnc arguments.
Also use the global variable explicit_display, set by the X server code,
instead of a private flag.
Signed-off-by: Carlos Santos <casantos@redhat.com>
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
The kernel_read_fs_sysctls interface does exactly the same thing and we
don't reinvent the wheel. It's also easier to maintain.
|
| | |
| | |
| | |
| | |
| | | |
We no longer restrict ourselves to just ASCII, so we need to tell
xgettext the encoding we use in the source code.
|
| | |
| | |
| | |
| | | |
This should have been included way back in 674bf06.
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Try to fix this error:
CMake Error at release/CMakeLists.txt:66 (add_dependencies):
Cannot add target-level dependencies to non-existent target
"tigervnc-Linux-x86_64-1.15.80.tar.gz".
The add_dependencies works for top-level logical targets created by the
add_executable, add_library, or add_custom_target commands. If you want to
add file-level dependencies see the DEPENDS option of the add_custom_target
and add_custom_command commands.
I get this error with cmake 3.31.7 and with cmake 4.0.2.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Allow everything to flush properly so that both ends see a clean close,
rather than a reset connection. Avoids misleading error messages.
|
| | |
| | |
| | |
| | | |
In case there are any last termination messages pending.
|
| | |
| | |
| | |
| | |
| | | |
The specification states that servers should reject invalid names (e.g.
IP addresses), so try to make sure we only set something valid.
|
| | |
| | |
| | |
| | | |
Better inform the peer why we are terminating the connection.
|
| | |
| | |
| | |
| | |
| | |
| | | |
If the peer decides to terminte the connection, then the reason will be
sent as an alert rather than seen through the normal error code. Make
sure we show this so it's easier to determine what went wrong.
|
| | |
| | |
| | |
| | | |
Just like we do for regular TLS communication.
|
| | |
| | |
| | |
| | | |
More avoiding duplication and increasing encapsulation.
|
| | |
| | |
| | |
| | | |
Let's avoid duplication and also raise the encapsulation a bit.
|
| | |
| | |
| | |
| | | |
We can use lambdas as glue and let them be normal methods instead.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Input and output do not happen independently in TLS streams, so we need
to have a coordinating central object for all I/O. E.g. a TLS read can
result in a low level write.
|
|/ /
| |
| |
| |
| | |
The ABI for the class needs to be stable across modules, so we cannot
have conditional class members like this.
|
| |
| |
| |
| | |
std::string doesn't like null strings. Give it an empty one instead.
|
| | | |
| \ | |
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Avoid releasing all keys if we're not losing focus for real. This is
useful if a keyboard shortcut is active when the keyboard is being
grabbed, as it allows chaining keyboard shortcuts.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It is now very likely that this happens as we will not have permission
to do this by default on macOS. So present a message to the user so they
understand why the keyboard isn't working as expected.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make this less complex by removing the timer and retrying things
synchronously. This can freeze the UI, but we give up after half a
second so it should hopefully not be noticable.
The advantage is that we can directly determine if we succeeded or
failed grabbing the keyboard. The previous code could in theory continue
retrying forever.
|