| Age | Commit message (Collapse) | Author |
|---|
|
This commit explicitly excludes certain targets from being built in a
unity build (or rather they continue to get built normally) as they
cause compilation errors in these kind of builds.
|
|
This effectively removes it as dependency.
|
|
This commit removes all qmake-related build-files from the system. We
have now migrated to cmake and are no longer maintaining qmake anyways
and therefore there is no reason to keep it.
Removing it also clearly states to any potential user/programmer that
this project is no longer intended to be compiled with qmake.
Given that the .pri files no longer exist, the mumble-version.py script
had to be adapted to read the version from the CMakeLists.txt file
instead.
Furthermore a few of the submodules support cmake natively and therefore
we no longer need the src/buid-directory approach in order to build
them. The respective build dirs have been removed and the src-dirs have
been renamed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
types in the future. Moved all crypto-related files into src/crypto.
|
|
The file is included by the "types.h" header.
Our CI builds with JACK never threw any errors because we install the development package.
|
|
|
|
|
|
|
|
"types.h" contains types we need, such as the various enums.
The header is added in a directory called "jack", so that the path (<jack/types.h>) matches the system one ("/usr/include/jack/types.h" usually).
|
|
CELT 0.11.0 provides better quality in comparison to CELT 0.7.0, but the two versions of the codecs are not compatible, which is why we provided both of them.
Opus was introduced in Mumble 1.2.4 (7586a61226a5477ff1f6418f51acdab65fe093f4), thus we expect that most (if not all) users are using it.
By removing CELT 0.11.0 we don't break backwards compatibility, because it's provided by CELT 0.7.0.
The main reason for removing the codec is the fact that its discontinued (in favor of Opus).
Also, CELT 0.11.0 was removed from the Debian package back in 2012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682010
|
|
We merged 3 pull requests in our fork:
- "Added CLang support": https://github.com/TsudaKageyu/minhook/pull/51
- "Add CMake support": https://github.com/TsudaKageyu/minhook/pull/58
- "Add <intrin.h> for MSVC": https://github.com/TsudaKageyu/minhook/pull/75
|
|
|
|
https://people.xiph.org/~jm/opus/opus-1.3
|
|
This commit adds all the missing includes when the PCH header is not used.
Also, some includes are reordered and/or made consistent (e.g. "#include <QtEndian>" -> "#include <QtCore/QtEndian>").
|
|
According to Qt's documentation the PCH header doesn't need to be included.
From https://doc.qt.io/qt-5/qmake-precompiledheaders.html:
"To make your project use precompiled headers, you only need to define the PRECOMPILED_HEADER variable in your project file."
"qmake will handle the rest, to ensure the creation and use of the precompiled header file. You do not need to include the precompiled header file in HEADERS, as qmake will do this if the configuration supports precompiled headers."
|
|
This is the behavior of "celt-0.7.0-build" and "celt-0.11.0-build".
We need it for "opus-build" too because we load it at runtime since e0ee016e5c333dabd2603b01decbe8ef2ae030e2.
|
|
|
|
variable length arrays
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
Consistently use single space before assignment operator.
|
|
Make them consistently two spaces indentation.
In two places a wrong indentation level was fixed.
|
|
|
|
This removes a section of opus-build.pro that sets the proper install name on the Opus shared library.
This commit removes it because it is not needed anymore -- we only ever build Opus as a static library on Unix-like systems.
|
|
|
|
This fixes the following error with MinGW on Linux:
../opus-src/celt/bands.c:31:20: fatal error: config.h: No such file or directory
#include "config.h"
^
|
|
|
|
win32/config.h"
|
|
win32/config.h"
|
|
of win32/config.h"
|
|
|
|
purposes.
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)
|
|
- Rename "HDE" folder to "hde", the name was changed in https://github.com/TsudaKageyu/minhook/commit/28338f33fac2a5a3162a461dd032b92189b1525f
- Use "$$SOURCEDIR" instead of manually specifying the folder name
|
|
Primarily to get MinGW support.
|
|
|
|
systems to 1.1.3.
|
|
This updates Opus to our mumble-voip/opus 1.1.3+msvc2013.3-alignment
branch.
Fixes mumble-voip/mumble#2146
|
|
This commit changes various pri and pro files to always prepend
the global build output directory (which can be either 'release'
or 'debug', depending on the current build configuration).
Otherwise, if a library that we build ourselves, such as -lspeex in
CONFIG+=bundled-speex, is also available in one of the other lib dirs,
we can't be sure that the one in our build output directory will be used.
This is a problem on FreeBSD, where we add /usr/local/lib
to the QMAKE_LIBDIR in compiler.pri. That directory might contain
its own -lspeex.
With this change, we now prefer libraries in our build output directory
to system libraries.
|
|
If we don't do it ourselves, qmake will add it automatically, and
warn to stdout.
The reason we need it here is because we use two VPATHs that include
files with the same names. That confuses nmake's inference rules, so
we have to disable them with no_batch.
|
|
ResolveRecord on error.
This fixes mumble-voip/mumble#2223
Before this commit, BonjourServiceResolver would not consistently
tear down the ResolveRecord when an error occurred.
The 100% CPU usage problem from issue 2223 happens in
BonjourServiceResolver::bonjourResolveReply, where previously,
the ResolveRecord was removed from qmResolvers for both error
and success -- but was never deleted on error. To fix this issue,
we delete the ResolveRecord for bonjourResolveReply's error case.
For constency, we also introduce similar code in the
BonjourServiceResolver::bonjourSocketReadyRead method.
Now, if DNSServiceProcessResult returns an error, we tear down
the ResolveRecord and remove it from qmResolvers.
|
