qmake: remove pointless use of raw data in $$[QMAKEFEATURES] access
property values are de-facto guaranteed to be backed by full QStrings, so there is nothing to be gained from using the raw data optimization, while doing so risks raw data leaks. Change-Id: I3d43da9aaadd4d5811c4b1a9d7ac734049da423c Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
This commit is contained in:
parent
14505bbfea
commit
18533ae2a7
@ -1517,7 +1517,7 @@ void QMakeEvaluator::updateFeaturePaths()
|
||||
feature_roots += m_option->getPathListEnv(QLatin1String("QMAKEFEATURES"));
|
||||
feature_roots += m_qmakefeatures;
|
||||
feature_roots += m_option->splitPathList(
|
||||
m_option->propertyValue(ProKey("QMAKEFEATURES")).toQString(m_mtmp));
|
||||
m_option->propertyValue(ProKey("QMAKEFEATURES")).toQString());
|
||||
|
||||
QStringList feature_bases;
|
||||
if (!m_buildRoot.isEmpty()) {
|
||||
|
@ -306,7 +306,6 @@ public:
|
||||
ProStringList m_returnValue;
|
||||
ProValueMapStack m_valuemapStack; // VariableName must be us-ascii, the content however can be non-us-ascii.
|
||||
QString m_tmp1, m_tmp2, m_tmp3, m_tmp[2]; // Temporaries for efficient toQString
|
||||
mutable QString m_mtmp;
|
||||
|
||||
QMakeGlobals *m_option;
|
||||
QMakeParser *m_parser;
|
||||
|
Loading…
x
Reference in New Issue
Block a user