| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
It is a requirement from hogweed, and we've apparently been lucky up
until now that the ordering was correct.
|
|
|
|
|
| |
The compiler does a fine job of this, so let's not try to duplicate that
effort.
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are generated during the cmake stage, but cmake thinks they are
generated during the build stage because of our rule to update the
timestamp on them. As a result, it thinks they should be removed when
doing "make clean".
There doesn't seems to be an easy way to tell cmake to leave these
alone. So instead, point cmake to a different marker file when updating
the timestamps. We don't care if that gets removed as it has no valuable
contents.
|
|
|
|
|
|
| |
GnuTLS seems to have dropped grypt support ages ago, so let's not
confuse things by assuming it might be needed when linking GnuTLS
statically.
|
|
|
|
|
|
|
| |
The previous method isn't compatible with CMake's try_compile() as it
will respect CMAKE_EXE_LINKER_FLAGS, but not CMAKE_C_LINK_EXECUTABLE and
friends. This results in the default libraries being completely missing,
and the compile test failing.
|
|
|
|
|
| |
These are expected to abort if they fail to find the relevant software
and "REQUIRED" is specified.
|
|
|
|
|
| |
We might not have all the necessary information, e.g. all targets might
not exist yet, until we're done going through all CMakeLists.
|
|
|
|
| |
They may be crucial, so refuse to continue if this happens.
|
|
|
|
|
| |
This is what the linker does, so we should do the same for correct
behaviour.
|
|
|
|
|
| |
Things might be in odd places, so make sure we respect where we're told
to look for libraries.
|
|
|
|
|
|
| |
We have internal dependencies that should be respected, as otherwise it
will be up to the user of the .la file to figure out the correct order
of the libraries.
|
|
|
|
|
| |
I think this only affects macOS at the moment where they also have .tbd
files for linking.
|
|
|
|
|
| |
We don't really use the .la files for macOS at the moment, but let's try
to be prepared.
|
|
|
|
|
| |
This serves no useful purpose as we have no reason to suspect there will
be a dangerous first character in these variables.
|
|
|
|
|
| |
Not sure how the old one ever worked as it incorrectly just tried to
match last character and nothing else.
|
|
|
|
|
| |
<target>_LIB_DEPENDS is an internal variable that contains lots of other
weird stuff.
|
| |
|
|
|
|
|
| |
pkg-config support was added very recently to gmp, so a lot of platforms
we want to support won't find gmp this way.
|
|
|
|
|
| |
It is a (weird) dependency of nettle, and not part of nettle itself. So
split it to a separate module for clarity.
|
| |
|
|
|
|
|
|
| |
This is the standard method of finding it on Unix systems, so make sure
we use it. Still keep a fallback, though, for other systems, e.g.
Windows.
|
|
|
|
|
|
| |
This is the standard method of finding it on Unix systems, so make sure
we use it. Still keep a fallback, though, for other systems, e.g.
Windows.
|
|
|
|
|
|
| |
We need this function to deal with pkgconfig files properly, but
unfortunately it doesn't exist until CMake 3.13, and we need to support
CMake 3.10. So add a hacky compatibility function for older systems.
|
|
|
|
|
| |
Without this change I get CMake errors due to use of ${FLTK_INCLUDE_DIR}
and references to the non-existent vncviewer target.
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
With this commit, TigerVNC will compile for Windows using MSYS2, MinGW-w64 and Inno Setup 6. The resulting binaries have some dll dependencies (even with BUILD_STATIC). The required dll dependencies are not included in the installer.
Unfortunately, the latest version of MSYS2 and MinGW-w64 do not produce a working executable for Windows 7.
|
|/
|
|
| |
Don't just build things, also test the various packaging.
|
|\ |
|
| |
| |
| |
| |
| | |
This is the current upstream so let's make use of it to get the latest
in features and fixes.
|
| |
| |
| |
| |
| | |
It's included by default in dynamic builds so we need to make sure it
isn't lost when switching to static.
|
| |
| |
| |
| |
| | |
Allows the user to perform certain important mouse operations using
touch gestures instead.
|
|/
|
|
|
|
|
|
| |
Switch from using Core events to using X Input events for pointer
devices in order to differentiate between mouse events and touch events.
Because FLTK doesn't understand X Input 2, we intercept these events and
translate them to core events where possible.
|
|
|
|
|
| |
This makes our builds directly compatible with most distributions
without packagers/users having to specify extra flags.
|
| |
|