Patch supplied by Helmut Grohne <helmut@subdivi.de> in Debian bug #919453https://bugs.debian.org/919453
Use set variable PKG_CONIFG to allow calling the pkg-config for the
architecture supplied in the build environment to allow cross building.
Patch supplied by Helmut Grohne <helmut@subdivi.de> in Debian bug #919453https://bugs.debian.org/919453
Use set variable PKG_CONIFG to allow calling the pkg-config for the
architecture supplied in the build environment to allow cross building.
Patch supplied by Helmut Grohne <helmut@subdivi.de> in Debian bug #919453https://bugs.debian.org/919453
Use set variable PKG_CONIFG to allow calling the pkg-config for the
architecture supplied in the build environment to allow cross building.
Patch supplied by Helmut Grohne <helmut@subdivi.de> in Debian bug #919453https://bugs.debian.org/919453
Instead of calling pkg-config directly, this patch calls pkgConfigExecutable()
from Qt5 to allow setting which pkg-config to be the one the user supplied
for the build to set the architecture to build with.
1. There are currently two servers appearing in a non-existent continent and country because their public IP addresses are part of two blocks assigned recently which are not in our GeoIP database.
This commit adds a new continent called "Unknown" without countries, which replaces the "ghost" continent and category.
2. If the user's public IP address was not in our GeoIP database, the "Unknown" continent and country categories were expanded because the strings resulted empty.
This commit adds a check to make sure that those categories are never expanded automatically.
Azure Pipelines offers many advantages over AppVeyor, with the biggest one being a maximum of 10 parallel builds for open-source projects, drastically reducing the builds completion time.
A pipeline takes about the same time to build on the two CI infrastructures, however the caching feature is currently only available on AppVeyor, meaning that on Azure Pipelines the compressed environment is downloaded for each build consuming about 10 minutes.
This means that we'll save at least 10 minutes per pipeline compared to AppVeyor once the feature is added to Azure Pipelines: https://github.com/Microsoft/azure-pipelines-tasks/issues/9190
Many users reported that no messages are shown in case Mumble is unable to access the microphone, aside from a simple message with the error code (0x80070005) in the developer console.
This is an issue because since Windows 10 1803 the privacy settings also apply to desktop applications, causing the microphone not to work anymore in many programs (including Mumble) if the user disables access to the microphone globally.
This adds messagelimit and messageburst to the configuration file murmur.ini as
well as the ability to set these live.
Though adjusting these live is entirely possible, they only take effect for new connections.
