baremetal: Fix detection of IAR toolchains if version contains build number

We need to allow the build number in the Version::fromString(),
otherwise it returns `unknown` version if a version ends with
the build number (i.e. when the version string contains  the
four parts <major>.<minor>.<path>.<build>).

Change-Id: Ic295d53d7a68a043ce1461cbe3c84c9502407dc2
Reviewed-by: Ivan Komissarov <ABBAPOH@gmail.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/src/app/qbs-setup-toolchains/iarewprobe.cpp b/src/app/qbs-setup-toolchains/iarewprobe.cpp
index 63d32bfc3..6c1506778 100644
--- a/src/app/qbs-setup-toolchains/iarewprobe.cpp
+++ b/src/app/qbs-setup-toolchains/iarewprobe.cpp
@@ -278,7 +278,7 @@ static std::vector<ToolchainInstallInfo> installedIarsFromRegistry()
                             const QFileInfo iarPath(rootPath + entry.subExePath);
                             if (iarPath.exists()) {
                                 // Note: threeLevelKey is a guessed toolchain version.
-                                infos.push_back({iarPath, Version::fromString(threeLevelKey)});
+                                infos.push_back({iarPath, Version::fromString(threeLevelKey, true)});
                             }
                         }
                         registry.endGroup();