CMake: Use Utils::FilePath in fileapi parser and reader

It still relies on local host execution in some places.

Change-Id: I36adfeb93ea26b285bbf6da2aee7e0fac64a7d94
Reviewed-by: Cristian Adam <cristian.adam@qt.io>
This commit is contained in:
hjk
2021-06-08 14:42:59 +02:00
parent 18a9df8b4a
commit d254cf5845
4 changed files with 63 additions and 54 deletions

View File

@@ -66,7 +66,7 @@ public:
QVector<ReplyObject> replies;
QString jsonFile(const QString &kind, const QDir &replyDir) const;
Utils::FilePath jsonFile(const QString &kind, const Utils::FilePath &replyDir) const;
};
class CMakeFileInfo
@@ -251,16 +251,16 @@ class FileApiParser
Q_DECLARE_TR_FUNCTIONS(FileApiParser)
public:
static FileApiData parseData(QFutureInterface<std::shared_ptr<FileApiQtcData>> &fi,
const QFileInfo &replyFileInfo,
const Utils::FilePath &replyFilePath,
const QString &cmakeBuildType,
QString &errorMessage);
static bool setupCMakeFileApi(const Utils::FilePath &buildDirectory,
Utils::FileSystemWatcher &watcher);
static QStringList cmakeQueryFilePaths(const Utils::FilePath &buildDirectory);
static Utils::FilePaths cmakeQueryFilePaths(const Utils::FilePath &buildDirectory);
static QFileInfo scanForCMakeReplyFile(const Utils::FilePath &buildDirectory);
static Utils::FilePath scanForCMakeReplyFile(const Utils::FilePath &buildDirectory);
};
} // namespace Internal