[Interest] QMAKE_FRAMEWORKPATH in qmake -query output

[Thiago Macieira]

On Sunday 11 January 2015 16:18:31 René J.V. Bertin wrote:
> #> qmake -query
> INCLUDEPATH:/opt/local/include
> INCPATH:/opt/local/include
> QMAKE_FRAMEWORKPATH:/usr/local/qt/5/lib
> QMAKE_LIBDIR:/opt/local/lib
> QT_SYSROOT:
> QT_INSTALL_PREFIX:/opt/local/libexec/qt5
> QT_INSTALL_ARCHDATA:/opt/local/libexec/qt5
> QT_INSTALL_DATA:/opt/local/share/qt5
> QT_INSTALL_DOCS:/opt/local/share/doc/qt5
> QT_INSTALL_HEADERS:/opt/local/include/qt5
> QT_INSTALL_LIBS:/opt/local/libexec/qt5/Library/Frameworks
> QT_INSTALL_LIBEXECS:/opt/local/libexec/qt5/libexec
> QT_INSTALL_BINS:/opt/local/libexec/qt5/bin
> QT_INSTALL_TESTS:/opt/local/share/qt5/tests
> QT_INSTALL_PLUGINS:/opt/local/share/qt5/plugins
> QT_INSTALL_IMPORTS:/opt/local/share/qt5/imports
> QT_INSTALL_QML:/opt/local/share/qt5/qml
> QT_INSTALL_TRANSLATIONS:/opt/local/share/qt5/translations
> QT_INSTALL_CONFIGURATION:/opt/local/etc/qt5
> QT_INSTALL_EXAMPLES:/opt/local/share/qt5/examples
> QT_INSTALL_DEMOS:/opt/local/share/qt5/examples
> QT_HOST_PREFIX:/opt/local/libexec/qt5
> QT_HOST_DATA:/opt/local/share/qt5
> QT_HOST_BINS:/opt/local/libexec/qt5/bin
> QT_HOST_LIBS:/opt/local/libexec/qt5/Library/Frameworks
> QMAKE_SPEC:macx-clang
> QMAKE_XSPEC:macx-clang
> QMAKE_VERSION:3.0
> QT_VERSION:5.3.2
> 
> The `QMAKE_FRAMEWORKPATH:/usr/local/qt/5/lib` line worries me: it's
> completely undesirable. When I noticed this the 1st time the path existed,
> but I get the same output after moving /usr/local/qt out of the way and
> even reconfiguring Qt 5.3 under that condition. I cannot find a hardcoded
> reference to anything /usr/local in my build tree, nor even how qmake
> constructs the contents of that variable, but I'm guessing it is determined
> at runtime regardless of what actually exists on disk?
> 
> Is there anything I can do (in terms of configuration or patches) to make
> QMAKE_FRAMEWORKPATH return the appropriate value?

It's not about your configure and this value is not hardcoded.

Given the position in the output (first of all), it's not coming from the 
built-in variables, but those loaded by the configuration. That is, those 
properties were once set with qmake -set.

        settings = new QSettings(QSettings::UserScope, "QtProject", "QMake");

That's the settings file you need to find.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center