| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
"libstdc++" was deprecated with Xcode 8 and is not supported in Xcode 10.
The new library is "libc++", available with macOS 10.9+.
https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes
|
|
|
|
|
|
Patch supplied by Helmut Grohne <helmut@subdivi.de> in Debian bug #919453
https://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.
|
|
each build file type
|
|
|
|
Qt 5.10 uses features available only on macOS 10.8, such as
std::future<void>.
See the referenced issue for more information.
Fixes mumble-voip/mumble#3288
|
|
Shelling out to dpkg-buildflags to get the preferred build flags
is now the way to go on Debian.
Previously, our PPA packages used hardening-wrapper to pass the
proper hardening flags to the package. That package is no longer
available in Debian unstable or Ubuntu zesty. To remedy that situation,
we have to add flags ourselves via dpkg-buildflags.
This commit implements a new CONFIG flag, CONFIG(dpkg-buildflags)
which will query dpkg-buildflags and append the retrieved CFLAGS,
CXXFLAGS, CPPFLAGS and LDFLAGS to QMAKE_CFLAGS, QMAKE_CXXFLAGS,
QMAKE_CPPFLAGS, QMAKE_LDFLAGS to ensure they are used in the Mumble
build.
|
|
The MinGW PR changed MUMBLE_ARCH to use QT_ARCH on Qt 5.
However, QT_ARCH uses 'i386' for 32-bit x86, we're currently
using 'x86' throughout our .pro files.
To fix this problem, we map 'i386' back to 'x86'.
This is currently breaking the win32-static (x86) build.
|
|
So that we use the G++ features when compiling with MinGW.
|
|
|
|
MXE's MinGW has the secure functions disabled by default, because their headers check if "MINGW_HAS_SECURE_API" is defined.
|
|
|
|
QMAKE_target.arch doesn't return "x86_64" with MinGW x64.
|
|
|
