qt-win-opensource-4.3.1-mingw.exe - qmake has my install path hard-coded into it

[marcel]

But what if the patching is done by the installer?
Look at option.h, from the qmake project:

class QLibraryInfo
{
public:
    enum LibraryLocation
    {
        PrefixPath,
        DocumentationPath,
        HeadersPath,
        LibrariesPath,
        BinariesPath,
        PluginsPath,
        DataPath,
        TranslationsPath,
        SettingsPath,
        DemosPath,
        ExamplesPath
    };
    static QString location(LibraryLocation);
};

class QLibraryInfo
{
public:
    enum LibraryLocation
    {
        PrefixPath,
        DocumentationPath,
        HeadersPath,
        LibrariesPath,
        BinariesPath,
        PluginsPath,
        DataPath,
        TranslationsPath,
        SettingsPath,
        DemosPath,
        ExamplesPath
    };
    static QString location(LibraryLocation);
};

To copy to clipboard, switch view to plain text mode 

This is the class used to access the paths. It is a minimal version of QLibraryInfo.

The paths are written by (and ONLY by) configure. Take a look in configureapp.cpp( from tools) in function Configure::generateConfigfiles(). Here is the only time those values are written somewhere.

This leads me to believe that the installer actually uses configure to initially configure the destination paths, and it modifies qmake.

There is no other explanation, or I don't see it right now.