|
FWIW, On macOS, Qt depends on knowing where it was compiled and built. It stores that info and will reguritate it as one of its paths and even uses it in macdeployqt. This is why on travis we need to use symlinks to get the Qt build to work with the Sigil build. So if qmake uses that compiled in home location but someone moved it into aQt5 subdir later (without a build), Qt would react the way you are seeing.
|