don't validate executable paths & working dirs in build & run configs
it's well within expectations that they do not exist at the time of configuration (especially when shadow building). additionally, keeping the validation info (macros and environment) up-to-date would require a notification infrastructure which is just not worth the effort.
Showing
- src/plugins/cmakeprojectmanager/cmakerunconfiguration.cpp 1 addition, 1 deletionsrc/plugins/cmakeprojectmanager/cmakerunconfiguration.cpp
- src/plugins/projectexplorer/customexecutableconfigurationwidget.cpp 1 addition, 1 deletion...s/projectexplorer/customexecutableconfigurationwidget.cpp
- src/plugins/projectexplorer/processstep.cpp 1 addition, 1 deletionsrc/plugins/projectexplorer/processstep.cpp
- src/plugins/projectexplorer/toolchainconfigwidget.cpp 1 addition, 1 deletionsrc/plugins/projectexplorer/toolchainconfigwidget.cpp
- src/plugins/qt4projectmanager/qt-desktop/qt4runconfiguration.cpp 1 addition, 1 deletion...gins/qt4projectmanager/qt-desktop/qt4runconfiguration.cpp
Loading
Please register or sign in to comment