Update the flags with our script extract-emojione-flags.py from the most recent emojione version 2.2.7.
Emojione changed from rectangle flags to round representations.
Fixes#2732
Previously, the mumble_flags.qrc was split into several files, generated
by mkflags.py. This will now generate only one qrc file because the svg
files are substantially reduced in size, all together 440.638 bytes in
size (so the workaround would actually no longer be necessary, and we
actually get only one qrc file).
I accidently neglected to rename this one instance to the new name in
MSVC2015. (The "msvcr" file is now "vcruntime".)
The rest of the references should be OK.
The Windows 7.1A SDK that is used when building with the v140_xp toolset
triggers the C4091 warning in multiple places. Instead of littering our
headers with pragmas, we ignore the warning everywhere via command-line
flag.
It shouldn't affect code quality. The x64 build doesn't ignore the warning
so we're bound to catch any warnings introduced in the future.
This fixes a problem with MinGW on Linux where it can't find the script file, because of the backslashes.
Windows handles the path correctly with both methods.
This fixes a problem with MinGW on Linux where it can't find the icon file, because of the backslashes.
Windows handles the path correctly with both methods.
This fixes a problem with MinGW on Linux where the "win32" block is triggered and the two backslashes are used, resulting in a path without slashes.
Python on Windows handles the path correctly with both methods.
It is unnecessary (the system has window-hiding built-in) and
can get us in a state where the window can't be shown again.
Easier just to leave it out.
The API of QSslDiffieHellmanParameters is frozen and will be available
in Qt 5.8.0.
Remove the safety-net of only allowing QSslDiffieHellmanParameters for
Mumble build environments.
The option currently works only on Linux, since there was no need in Windows, until now.
During a MinGW build test we noticed that minhook can be compiled only with MSVC, for various macros and probably other things.
warning: converting to non-pointer type 'procptr32_t {aka long unsigned int}' from NULL [-Wconversion-null]
ql\ql.cpp:87: warning: comparison is always true due to limited range of data type [-Wtype-limits]
sto\sto.cpp:11: error: 'numeric_limits' is not a member of 'std'
Not fixed:
sto\sto.cpp:55: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
Without this, we delay the log messages from -limits
until we exit with a qFatal.
This isn't good, because -limits *can* fail in ways that
cause it to get stuck. One example of this is when Murmur
runs out of memory. This typically happens on 32-bit systems
during the test that counts the number of threads Murmur can
spawn, given the system's resource limits.
One such instance is if we reach the virtual memory limit on
i386. Then, QThread::start() will try to call pthread_create(),
which fails with EACCESS. (Insufficient resources, system-imposed
or otherwise). Qt doesn't handle this error situation, but
instead calls qWarning to make the user aware.
Without this change, we would never present this warning to
the user, because Murmur would be stuck.
With this change, the user can at least see the warning, to
know something has gone wrong.
Fixesmumble-voip/mumble#2752
Previously, the python.pri helper would try to query which python
binary on the system to use via the 'which' command.
Some systems do not have which (some Docker-based CI systems,
for example).
We now detect the presence of 'which'. If it is not available,
we try to use 'python' as the Python command. We also print a
warning about 'which' not being available -- as well as a message
pointing users to the MUMBLE_PYTHON environment variable.
Fixesmumble-voip/mumble#2748
