* fixes for Go 1.13 + retain go module 1.12 GOPATH behavior for internal/examples
* update docker images to 5.13.0
* new docker images (windows_64_shared_512, linux_512, darwin_512)
* update examples to match the Qt 5.13 api
* bump android minSdkVersion to 21 (5.0 / lollipop)
* bump OpenSSL version for android docker deployments to 1.1.1a
* let the binding use the 513 env by default
you can use QT_VERSION=5.12.0 and/or QT_API=5.12.0 to keep the binding backward compatible with your code
just setting QT_API=5.12.0 alone should also be sufficient to keep docker deployments working
if you did install an official Qt version then just set the correct QT_VERSION and procede as usual
these changes should make the life of all newly incoming developers (or consumers of applications build with this binding) way easier
all one needs to do now is to install Git, Go and an C/C++ compiler then the binding can be setup by running:
go get -v github.com/therecipe/qt/cmd/... && $(go env GOPATH)/bin/qtsetup
or if one is only interested in building a specific application:
go get -v github.com/therecipe/qt/cmd/... && $(go env GOPATH)/bin/qtdeploy test desktop github.com/therecipe/examples/basic/widgets
for this to work, the tooling now recognizes a pkg path and "go gets" the package if necessary
beside these changes, the deployed binaries are now properly stripped on linux and console debugging is now enabled by default on windows
recursive dependency resolution for qtrcc
fix ci qtmoc issue
support for fluid + demo
support for kirigami + demo
init files for c++ modules
new webkit 5.8.0 *.index file
1. the qt api changed in various places
2. dropped the "_minimal" suffix for the deployment folders
3. to keep using older versions of Qt (5.7.1 for example), one would
now need to explicit export "QT_VERSION=5.7.1" and also
"QT_DIR=/path/to/Qt5.7.1"
