Add
- MYSQL_OPT_SSL_ENFORCE
- MYSQL_OPT_SSL_VERIFY_SERVER_CERT
- MARIADB_OPT_TLS_PEER_FP
- MARIADB_OPT_TLS_PEER_FP_LIST
options to control the SSL behavior.
Especially to disable SSL you need to set
MYSQL_OPT_SSL_VERIFY_SERVER_CERT to false on macosx.
Replace the @rpath/libmariadb.3.dylib by "$INSTALL_DIR"/lib/libmariadb.3.dylib
in the self compiled plugin "libqsqlmysql.dylib" after installation in the
QTDIR plugin directory.
This provokes macdeployqt to install libmariadb.3.dylib to take
libmariadb.3.dylib into account and also install it and resolve all
referenced library paths.
Finally the absolute path will be replaced by the @rpath when
creating the xca.app.
Add tests for my HOME dir inside the installed binaries to
detect errors in the future.
Stay with QT 6.6.3 on Windows, because windeployqt
does not deploy the gcc libs with QT 6.7.2
Stay with QT 6.6.3 on MacOS, because the info/warning
message does not show an icon
Add the name from the "provisionprofile" to the
entitlements to silence the error and allow
testflights.
Extend legacy.dylib to also include the x86_64 binary
Bump patch version to get new versions
even with commit amending.
APPSTORE_COMPLIANT = ON:
- Turns off the File menu and moves the language selector to
the "Extra" Menu. "Options" and "Exit" are at the xca-macos
special-menu anyway.
- Switches the signing key from "Developer ID Application" to
"3rd Party Mac Developer Application"
- Sets the database name to "default.xdb"
- Adds "-appstore-compliant" option to macdeployqt
- Picks the "entitlement-appstore-compliant.plist"
- Disables the "Token" menu and "PKCS#11 provider" tab
in the option dialog
It only builds "x86_64":
$ file build-sqlplugins/plugins/sqldrivers/libqsqlmysql.dylib
build-sqlplugins/plugins/sqldrivers/libqsqlmysql.dylib: Mach-O 64-bit bundle x86_64
Building with -DCMAKE_OSX_ARCHITECTURES="x86_64;arm64" has no effect.
Neither has './configure -- -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"'
Even './configure -- -DCMAKE_OSX_ARCHITECTURES="arm64"' only builds
x86_64 plugins.
git.release.something ->
Create any git release with a tag to test package (debian/rpm) build
git.release -> Create required changes and tags for the next release
git.publish -> Finalize the release (github release)
gen-binary-hash / binary-hashes.json -> keep track of release hashes
