Folder structure of Qt SDK

[wysota]

I think it's a good idea, actually.

It's not but have it your way...

Let's treat it as an exercise, can we?

Be my guest.

There should be nothing magical about moving a product which is thought of as drop-in installation according to your own words

It's practically a drop-in installation. There is nothing magical apart the need to patch paths in qmake and a bunch of other files which is exactly what the "installer" does.

Do you have any information on where and how is configuration of qt framework stored so that I could update it after moving qt?

It's embedded into qmake binary. You'd have to patch it or rebuild qmake with the proper paths. Which is one of the reasons for such things not being good ideas.

How could qmake know the installation directory

I guess I already answered that...

[piotr.dobrogost]

It's the first drop-in installation I see that remembers, in binary file (sic!), where it was installed and thus can't be freely moved...

Could you please comment on my post #13?
http://www.qtcentre.org/forum/p-fold...stcount13.html

[wysota]

Could you please comment on my post #13?

I already did - the path is hardcoded into qmake so that you can have different installations of Qt and switch them by activating different qmakes.

Correct me if I'm wrong but you are passing an invalid path to -spec and expect it to work, right?

[piotr.dobrogost]

I already did - the path is hardcoded into qmake so that you can have different installations of Qt and switch them by activating different qmakes.

Bizzare way of customization I have to admin.
Why to hardcode any path?
Couldn't just qmake read specific environment variable?
Wouldn't that be more flexible solution?

Correct me if I'm wrong but you are passing an invalid path to -spec and expect it to work, right?

No. I can't change -spec parameter direclty from within Qt Creator. I thought it would have been taken from QMAKESPEC environment variable so I set it properly to c:/qt/4.5.2/mkspecs/win32-g++\qmake.conf However this doesn't change anything; Qt Creator still shows old, wrong path to the specification file.

[wysota]

Bizzare way of customization I have to admin.
Why to hardcode any path?
Couldn't just qmake read specific environment variable?
Wouldn't that be more flexible solution?

It does read environment variables. But in case one isn't provided it can either refuse to cooperate or do something useful. It does something useful. Unfortunately Windows doesn't support links in its filesystem as this would be even simpler.

No. I can't change -spec parameter direclty from within Qt Creator. I thought it would have been taken from QMAKESPEC environment variable so I set it properly to c:/qt/4.5.2/mkspecs/win32-g++\qmake.conf However this doesn't change anything; Qt Creator still shows old, wrong path to the specification file.

Well... works for me (note the last part) when I set the specs manually:

Starting: /usr/bin/qmake /home/(...)/appserver.pro -r CONFIG+=debug -spec bogusspec

Still doing things properly is probably a better idea. I don't know why you're so eager to separate the installation into two parts when there is one that is already separated and would work perfectly fine for you.

[piotr.dobrogost]

Can you take a look at Projects/Build Settings/Build Steps settings in creator and tell me where the value of -spec parameter is taken from?

[wysota]

It's taken from qmake -query QMAKE_MKSPECS but I'd advise to take the source code of Creator and check that our yourself.