On Saturday 21 November 2015 17:17:49 René J.V. Bertin wrote: > That would mean having 2 different Qt5 installs in MacPorts; one for pure Qt > applications that are expected to behave "natively"
I still have to see proof that a "pure Qt application" installed with MacPorts really cares about where QSP points to - apart from the obvious migration issue if this ever changes. I keep having the feeling that the simplest solution is to consider MacPorts a different "platform" than OSX, in terms of paths. For sure the install path of an app installed via MacPorts will be something like /opt/local while a real OSX Qt app wouldn't go there. So can't it live with settings in ~/.config and data files in ~/.local/share etc.? Otherwise, the next best idea is to get ECM to add your activator to all link lines automatically, e.g. by adding it to CMAKE_EXE_LINKER_FLAGS or whatever. This for sure beats editing every link line, or trying to guess which frameworks are going to be "used by everyone". -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel