NOTE: I cannot bundle the Qt Visual Studio Tools natvis file into the extension itself because of it's license restrictions (MIT vs GPL)! When you set an url, the extension will only download it ones and cache it and will use the cached local version you can set qttools.visualizerFile to the natvis file from the offical Qt Visual Studio Tools ).
You can also set your custom created/downloaded qt natvis file instead of the bundled one (which implement a few Qt types) by setting qttools.visualizerFile to a filepath or url (f.e. If you don't like that feature you can turn it of via qttools.injectNatvisFile setting. The Qt natvis file from this extension will automatically get injected into your existing launch.json file (per default).
Debugger extensions (via natvis files).Extract the Qt file locations via PATH environment variable.Extract the Qt file locations from the cmake cache.You can set the executable path via qttools.creator settings if the extension can't find Qt Creator (for whatever reason) This extension try to detect the Qt Creator installation automatically (on Windows and MacOS). You can also open the whole workspace in Qt Creator too. The extension supports Qt file location extractions viaĬhoosing a different Qt version from disk via this extension is not supported! Features It is designed to be a similar tool to the Qt Visual Studio Tools from The Qt Company, but it tries to cooperate with other extensions for some functionality like e.g. This is NOT an official tool by The Qt Company!! This extension is work in progress, so some command/settings can change over time.
0 kommentar(er)
