`qmake` is better suited for finding `windeployqt`, since it's in the same
directory as `qmake` on windows.
`qmake` is also better suited for finding the build target
(release/debug) vs third party scripts.
`windeployqt` is being forced to run in `cmd` because the syntax is
different for running executables in powershell, which means
`windeployqt` won't be executed and runtime or package errors will
occur.
With the removal of the windeployqt call the deploy step is no longer
needed for building on Windows, since all previous deploy tasks are now
handle by Qmake.
Described in commit 97e203fd89e7cb54c7ce96ce779b2e8cb6ac1374
The python functions are no longer needed since the python script
doesn't handle file copy any more.
Described in commit 97e203fd89e7cb54c7ce96ce779b2e8cb6ac1374
The linux directory in package_files is included even on Windows install
for simplicity and because it takes up less than 1KB.
This should solve problem
https://github.com/probonopd/linuxdeployqt/issues/25
with error message
QML Error:
file:///tmp/.mount_OpenVRtQNnT6/usr/bin/res/qml/common/mainwidget.qml:1:1:
module "QtQuick" is not installed
CircleCI Xenial does not come with an up to date version of Clang. It is
therefore required to get the newest version (8). The .pri file has
quickly been edited to be similar to the g++ version check.
* added arbitrary orientation change
* removed commented code
* updated to OVR 1.4.18
* changed two instances using new to init via array
* moved prox sensor action to haptic instead of Misc
* fixed json file, added prox sensor back for mic mute/un-mute
* added proximity sensor to audio and haptic chaperone warnings
* fixed fall-through behavior
* removed bad prox code
The media keys were only in the keyboard shortcuts file because their
implementation was the same. With Linux support incoming their
implementations are not necessarily the same.
Manually creating an RC file was the Qt 4 way. The Qt 5 way is just
giving it an icon.
When an RC_FILE isn't manually created Qt will attempt to create one. If
there are non-integers in the version number the compilation will crash.
AdvancedSettings_resource.rc is a build artifact on Windows.
This allows Qmake to use the version number as well as not requiring all
other uses of the version string to strip double quotes from it. This
also reduces the fragility of the version string as it was required to
be a valid C++ char*, even in contexts where that wouldn't matter.
Users do not care about commit numbers and it only serves to confuse
them. Release builds should not contain build metadata since there
should only be one definitive version.
SemVer 2.0.0 requires a plus for build metadata.
https://semver.org/
`Build metadata MAY be denoted by appending a plus sign and a series of
dot separated identifiers immediately following the patch or pre-release
version. Identifiers MUST comprise only ASCII alphanumerics and hyphen
[0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata SHOULD be
ignored when determining version precedence. Thus two versions that
differ only in the build metadata, have the same precedence. Examples:
1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85.`
Vasily
ykeara