Quote Originally Posted by Asperamanca View Post
This is pure semantics, but I stated


(there was more, but this is the core of the statement)
Which is false. Prior executions of qmake have nothing to do with contents of one of included files. It's not qmake that made changes to those files, it only modifies Makefiles (and creates a .pro file when run with -project switch).

If (as I now know) there is a mechanism to pre-define those values for all projects (using qconfig.pri), then my statement is basically correct: The value of the SOURCES variable can be remembered across multiple project, machine reboots, etc.
Which, again, has nothing to do with prior executions which was the essence of your statement. You can modify qconfig.pri (or any other included file) and run qmake once and it will "remember (nonexisting) prior executions".


Of course the description is misleading, since I did not (at that time) know the cause for this behaviour, and thus used the term "remembering", which is inaccurate.
On the other hand my "impossible" statement was accurate because the only file opened in write mode by qmake is the Makefile. It doesn't do any caching on its own.

EDIT:
As for IDE...I'm using QTCreator, which (right now) seems to be the most likely cause.
I think so as well, Creator likes to modify wrong project files when you add a file to a project. If you had Qt opened as a project and config.pri was mentioned there somewhere explicitely and you tried adding a file to some project, it might have accidently landed in qconfig.pri. That's a bug in Creator, for sure