summaryrefslogtreecommitdiff
path: root/src/plugins/cpptools/cppcodegen_test.cpp
diff options
context:
space:
mode:
authorEike Ziller <eike.ziller@qt.io>2021-08-27 10:08:07 +0200
committerEike Ziller <eike.ziller@qt.io>2021-08-31 06:50:15 +0000
commite465d182151f12885fd2c977563587da2eb40877 (patch)
treede45d2d0401e401607d987523a5d3b7f0ccd952b /src/plugins/cpptools/cppcodegen_test.cpp
parent99399ab6ee84377ad0c1ec782120d66ea13287d7 (diff)
downloadqt-creator-e465d182151f12885fd2c977563587da2eb40877.tar.gz
Always set an environment for QtcProcess
Since e755094480b1775c2b7b794766a8170ae03c85f6 we have a global option in Qt Creator to set the (base) environment for any tools run by Qt Creator. So it is expected that any tool actually uses Environment::systemEnvironment() as a base, which is the system environment modified by the global option. QtcProcess already had a fallback to Environment::systemEnvironment for resolving environment variables in Qt Creator macros in the command line. Also use it as a fallback for the actual environment for the process. Latest occurrence where the global environment setting was ignored was for starting language servers by our LSP client. Change-Id: Id1a4141326d8ef3239b37d7f3daf21928605ca92 Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
Diffstat (limited to 'src/plugins/cpptools/cppcodegen_test.cpp')
0 files changed, 0 insertions, 0 deletions