GitLab

Reviewed-by: Daniel Teske

if the exact evalution fails (possibly because of a parser error), then
still use the cumulative evaluation to construct the project tree. only
the target information won't be updated and the code model will be left
in the dark.

todo: the errors are dumped only to the (unnumbered) "general messages"
output pane, which makes them practically invisible.

Task-number: QTCREATORBUG-3093

it would collect global values instead.

special-casing it makes no sense, as all other values from the
project would be mismatched and thus worthless for code validation
anyway.

the node updater would check if the cumulative and exact evalutor
returned the same project type and would discard the cumulative one if
they didn't. this was pointless, as a) it would practically never happen
and b) it would be without much consequence anyway.

... otherwise oldValues equals newValues.
the signal is currently not connected anyway, but whatever.

Task-Nr: QTCREATORBUG-2166

The build actions are disabled if the buildconfiguration is disabled.
The deploy and run actions are disabled if deploying or running invokes
building automatically.

Qt4BuildConfigurations are disabled while parsing.

Task-Nr: QTCREATORBUG-2576

Reviewed-by: hjk

The proper fix would be to support the QMAKE_SUBSTITUTES variable.

Guard access to pointer, which happens to be 0. The regression
was most likely introduced by 057591e0.

On a change to the deployment folder, we need to run qmake again to
recreate the pkg file, we do that by setting a flag on all qmakesteps
for symbian and saving/restoring that flag.

Reviewed-By: hunger
Task-Nr: QTCREATORBUG-3062

For larger projects, it doesn't make much sense without mentioning
the respective project file.

promptReadOnlyFile: EditorManager-->FileManager
fileFilters: EditorManager-->MimeDataBase
saveFile & saveFileAs --> IFile based

Ignore folders from cumulative parse, we are recursively enumerating all the
files from those folders and add watchers for them, that's too dangerous
if we get the foldrs wrong and enumerate the whole project tree multiple
times.

Task-Nr: QTCREATORBUG-3104

Reviewed-By: con
Reviewed-By: Alessandro Portale

Task-Nr: QTCREATORBUG-3014
Task-Nr: QTCREATORBUG-2821

Normally, we print a debug message about INSTALLS += var
with var.files being empty.
Don't do this if var.CONFIG contains "no_check_exist".

Task-Nr: QTCREATORBUG-3001

Krazy was complaining about those.

Initial patch and idea by hunger.
Reviewed-By: hunger

Instead, utilize the newly added INSTALLS information of Qt4ProFileNode.

Task-number: QTCREATORBUG-2679

Task-number: QTCREATORBUG-2679
Reviewed-by: dt

Might, or might not fix
Task-Nr: QTCREATORBUG-2361