This is due to a change in the behaviour of clang-cl in LLVM 6.0
where `-Wall` became a synonym for `-Weverything` to be more like
the behaviour of `/Wall` in the Microsoft compiler. `/W4` is the
new way to spell `-Wall -Wextra`.
The config is loaded from json files by qmake, and we define the qmake
function `swiftConfig` for checking whether a feature is enabled.
This function can be directly used in `buildconfig_gen.cpp.in`,
so the trick with C++ comment tokens in variables is not needed.
This necessitated moving some function definitions into a .inc file
that is included by buildconfig.h, as constexpr functions must be defined
in the header. This new file is added to the list of QMAKE_SUBSTITUTES.
* QStringLiteral expects UTF16 for MSVC compilers
* we use descriptive names now
* UTF flag for MSVC compilers
* added the SLACK discussion as comment under https://dev.swift-project.org/T404
This aligns the behavior and concept with the 32 bit FSX version. SimConnect
is loaded at runtime, depending on the version being selected.
It also adds a featuren to change the P3D SimConnect version at runtime by
unloading the previous and loading a new one.
ref T349
Previously the FSX/P3D driver tried to link a very specific SimConnect version
from the Windows Assembly cache. This caused issues with machines
which did not have this specific version of SimConnect in the assembly
cache since drivers refused to load without much information. Having a different
version of SimConnect in the assembly cache or even in the bin folder did
not help.
To fix this problem, SimConnect is now loaded and resolved manually at
runtime. This allows to try loading different versions from the assembly
cache or prefer to load the shipped one.
For this, the manifests are linked into the binary's resource section and
activated manually before loading. This has the positive effect, that
loading errors can be handled by code instead of raising a cryptic error and
aborting.
Summary:
Only blackcore includes the headers of crashpad. It is therefore
not necessary to add this include paths globally for all projects.
Reviewers: #swift_pilot_client, kbasan
Reviewed By: #swift_pilot_client, kbasan
Subscribers: jenkins
Differential Revision: https://dev.swift-project.org/D70
Summary:
- Changed the name in all build artifacts
- Everywhere in C++
Reviewers: #swift_pilot_client, kbasan
Reviewed By: #swift_pilot_client, kbasan
Subscribers: jenkins
Maniphest Tasks: T205
Differential Revision: https://dev.swift-project.org/D69
Summary: By qualifying the key with `isEmpty` it prevents overwriting a value specified on the commandline.
Reviewers: rwinklmeier
Reviewed By: rwinklmeier
Subscribers: jenkins
Tags: #swift_pilot_client
Differential Revision: https://dev.swift-project.org/D51
Summary:
Configuration tests check whether all mandatory dependencies to build
swift are met. They can also be used to check optional dependencies, which
results in certain features to be enabled or disabled.
This first batch tests for mandatory libraries libpng, zlib and OpenGL.
If this is not tested and some libraries are missing, the developer will
be notified very late in the build.
Reviewers: #swift_pilot_client, msutcliffe
Reviewed By: #swift_pilot_client, msutcliffe
Subscribers: msutcliffe, jenkins
Differential Revision: https://dev.swift-project.org/D34
Summary:
This fixes issue reported by Klaus in Slack:
> when I change something in the plugin driver, I always have to rebuild the plugins before I can debug again.
Also refactored `libraries.pri` to remove duplication.
Reviewers: #swift_pilot_client, rwinklmeier
Reviewed By: #swift_pilot_client, rwinklmeier
Subscribers: kbasan, jenkins
Tags: #swift_pilot_client
Differential Revision: https://dev.swift-project.org/D31
Summary:
This commit enables P3D-v4 for 64 bit including all dependent libraries.
Those binaries are not yet installed, since they are considered
experimental.
Reviewers: #swift_pilot_client, msutcliffe
Reviewed By: #swift_pilot_client, msutcliffe
Differential Revision: https://dev.swift-project.org/D30
Summary:
If FSUIPC is configured, its support will be enabled in swift
and disabled otherwise.
Ref T91
Reviewers: #swift_pilot_client, msutcliffe
Reviewed By: #swift_pilot_client, msutcliffe
Subscribers: msutcliffe, jenkins, kbasan
Maniphest Tasks: T91
Differential Revision: https://dev.swift-project.org/D28
The hardened vatlib requires to use server type VATSIM (which configures
the VATSIM protocol in vatlib) to connect to VATSIM servers. Using
any other server type will from now on fail to connect to VATSIM.
Since unit tests regularly run tests against the server running on VATGER, this has to be enabled
change the default server type to VATSIM by enabling SwiftVatsimSupport.
