OK, I figured this out. With the risk of kicking in open doors: - the maintenancetool/MaintenanceTool binary is "just" the installerbase executable. On Mac it will be modified to depend on embedded Qt frameworks by the actually installer when it writes the MaintenanceTool bundle, but it fails to embed those frameworks because they weren't bundled with the other installer data. Suggestion: use macdeployqt to create a fully functional MaintenanceTool.app bundle during the initial creation of the installer.
- the information required to run the MaintenanceTool on the installed software is expected under the same name as the tool itself. - An up-to-date self-built MaintenanceTool.app copy will continue to fail with the message that it's out-of-date because the tool version is not obtained from the app itself, but from the database of installed items. IMHO that's an anomaly. R. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest