Change our checks for MUMBLE_NO_PCH to use string comparisons
instead of numerical comparisons.
When MUMBLE_NO_PCH is not set, the numerical equivalent check
fails because nothing is on the left-hand side of the -eq operator.
Fixesmumble-voip/mumble#3314
We used to use DIST for referencing extra files that should be included
in our tarballs created by 'make dist'.
However, we've since migrated away relying on 'make dist' in release.pl.
Instead, we include everything, and have a list of items to exclude, such
as IETF RFC drafts distributed in 3rdparty/speex-src that do not adhere to
the Debian Free Software Guidelines.
This commit adds a new script for generating PEM forms
of the Diffie-Hellman groups in RFC 7919.
RFC 7919 specifies a set of Diffie-Hellman groups that
can be negotiated by TLS 1.1 and 1.2 servers and clients
using the same mechanism that is used for named elliptic
curves in TLS.
Our TLS implementation doesn't support RFC 7919 at present,
but we can still use the groups defined in the RFC as good
reference Diffie-Hellman parameters for Murmur, since they
are audited and may be more resistant to attacks than ones
randomly generated.
This ensures that murmur.ini on Windows installations has
Windows-style line endings, allowing admins to use Notepad
to edit the file.
Fixesmumble-voip/mumble#3101
This ensures that the output of the script is consistently sorted.
This commit uses the integer value of the literal cipher suite value.
This will make future diffs from output of the script much easier to read.
This commit adds a Homebrew-based macOS build to our Travis CI build
matrix.
It also cleans up the exising build matrix such such that Linux builds
are built only on Linux hosts, and macOS builds are only built on macOS
hosts.
This PR fixes a recently introduced no-pch error in Meta.h.
It also adds a no-pch configuration to Travis CI so we can catch these beforehand in the future.
On Windows, it is not always possible to create a relative path from an
absolute path. For example, if Qt lives on C:, and Mumble is being built
on Z:.
Things will fall apart then, because we include some of Qt's
translations in our .qrc files.
This commit works around that issue by falling back to absolute paths
when finding a relative path fails.
Using SQLite's WAL (write-ahead log) can create less disk I/O while
still providing good consistency and durability.
This change uses SQLite's WAL with synchronous=NORMAL which can
cause loss of transactions on power failure. Only the transactions
which haven't been synced to the disk by the OS are lost. The
database itself will still be in a consistent state, but it might
not have all recent changes.
The class implements an API similar to OpenBSD's arc4random:
- A way to get a random uint32_t. (arc4random)
- A way to get a random uint32_t with an upper bound. (arc4random_uniform)
- A way to fill a buffer with random data. (arc4random_buf)
The current configuration uses a hacked up
win64-static-no-ltcg build environment until we
build our next set of real ones. As we do not want
to distribute our build env at this point the source
is obfuscated for now.
We utilize the appveyor cache to cache the compressed
build environment we downloaded. We do not cache the
uncompressed variant to save the time it takes to package
it up in case of cache invalidation. Cache invalidation
is keyed on changes to the appveyor.yml .
With the current setup, OpenBSD 6.0's g++4 on a VM with 4GB ram can't even
build Mumble, because the generated .cpp file from mumble_flags.qrc is
32MB.
This commit attempts to work around that by splitting our SVG flags into
separate resource files.
To make it easier to work with from the qmake build, we now also generate
a mumble_flags.pri file that will automatically add all necessary .qrc
files to RESOURCES.
This removes a lot of very hacky stuff. Its own job was to
let the manual plugin be a separate DLL.
Now that the manual plugin is built into Mumble itself, all
these dirty tricks can be removed.
Since we don't have to export a lot of symbols that we don't
use anymore, the linker can remove a lot of unused code for us:
mumble_app.dll before (1.3.0~969): 40.345 KB
mumble_app.dll after: 36.819 KB
Difference: -3.526 KB
As-is, the murmur.ini.system used by our PPA builds
(and Debian-based distros) are broken because the
script doesn't set the "logfile" and "pidfile"
options.
The email capture group accidently captured
the whole email part of the contact, including
angle brackets.
Update the capture group to only capture the
actual email address.
We have no use for this script that converts
.ts files to .html for easier human consumption.
We now use Transifex for even easier localization.
Delete the file.
Previously, qt.conf was used to sepecify the runtime
plugin path for Qt in our dynamic Windows and OS X
builds.
Now that those builds use static Qt, the file is
unused.
Delete it.
My own rule of thumb for scripts in our repo is to keep the
number dependencies down. In practice, this means I always
strive to only use the standard library.
In this case, it's not that easy.
The existing code sorted sufficiently on Windows.
However, when run on Unix-like systems, it produces odd, and
to my mind, unexpected sorting behavior. (Such as ignoring spaces,
and sorting 'Hey You' after 'Heyh You'.)
I suppose the sort order is a matter of preference.
But the non-determinism of the script's output isn't.
If we don't fix this, we'll get noisy diffs once in a while,
which isn't very nice.
This commit changes the script to use 'pyuca' to
do the sorting. This is a pure Python module, so
it's easy to install via pip on all OSes.
This adds a dependency on a small library, XInputCheck, which is
a function abstracted away from SDL. All it does is check whether
a given DirectInput guidProduct is an XInput device.
This simplifies the LICENSE file refer to the copyright
holders of Mumble as "The Mumble Developers". The client
already does this in the About dialog.
The entity "The Mumble Developers" is the name we use for
the copyright holders of Mumble. These are listed in the
AUTHORS file.
The AUTHORS file is generated via scripts/generate-AUTHORS.py.
The script looks at the Git history and removes duplicates and
other mistakes made through the years.
All new files in the repo should use the license header found
in LICENSE.header.
The AUTHORS and LICENSE files are permalinked to
https://www.mumble.info/LICENSEhttps://www.mumble.info/AUTHORS
These locations are used in the files themselves,
as well as the license header.
While the FamFamFam icons have served us well, we really
need SVG flag icons for HiDPI scenarios.
This is one of the last pieces missing to allow us to
claim we fully support Retina displays on OS X.
In each generated file we want to have a banner that warns of
modification by hand and indicates the generator responsible
for the file. This patch extends mkwrapper.pl to write such
a header.
It also switches mkwrapper.pl away from barewords for file-handles.
Apparently those are no longer considered idiomatic Perl and they
broke the "iterate over list of handles" thing this patch does.
This change removes our qmake-based Qt translation embedding.
That system uses mumble_qt.qrc resource file with
hardcoded filenames for Qt translations, and some logic
implemented in qmake that copies Qt translations into
the Mumble source tree such that the paths in the
mumble_qt.qrc file match.
The new system introduces a simple Python script that
takes an output filename for the .qrc file the tool
will write, along with a set of directories containing
Qt translations.
The tool will generate a Qt resource file containing
references to all the translation files found in the
specified directories. However, the tool takes care
to only include language files once.
In typical use, the first directory parameter passed
to the tool is the QT_INSTALL_TRANSLATIONS directory,
which is where Qt stores its own translation files.
The second directory is Mumble's fallback directory.
The tool then goes through all files in the first
directory, and notes down which languages have been
processed. Multiple files for a single langauge can
be included from the a directory (qt_help_da.qm,
and qtbase_da.qm), but once a language has been
added from one directory, it will not be added
if found in the next one in line.
We use this to include a set of 'fallback'
translations for versions of Qt that do not
include them. This also allows this new style
of Qt translation embedding to be forward
compatible with newer versions of Qt that
add new translations.
Once Qt includes a translation that we have
in our fallback directory, the Qt translation
is used instead.
