| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
Some Qt installations do not have `qmake.exe` but `qmake.bat` instead.
This commit adds a check for `qmake.bat` in the Qt installation
directory.
Fixes: VSCODEEXT-117
Change-Id: I2d4aa5fdda216739be16bc3a95867496d2817561
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit e69b51c7caa1e4f05ea4e7d98b1de7647d6dff73)
|
| |
|
|
|
|
|
|
|
|
| |
During the startup,`qt-qml` and `qt-ui` should wait until `qt-cpp`` sets
the initial configuration values. Otherwise, qt-qml qt-ui may not be
able to access the correct configuration values.
Change-Id: I974a0e5e7e9cb541ea4a382ac85c303b6b59646f
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
(cherry picked from commit 1249ef41807b826884e4059f4c4706a1980fbe2a)
|
| |
|
|
|
|
|
|
|
|
|
| |
Since event handlers are not disposed properly, they are still active
when the project is closed. This can cause those handlers to be called
after the project is closed, which can lead to errors.
* Dispose project managers inside `Deactivate()`
Change-Id: Idd7b8548f7c16c41c0e4fd7052fa7ae988678bc4
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
When only the value is checked whether it is undefined or not, it
doesn't give us the correct result because the value either can be
set to undefined or not set at all. We get undefined in both cases.
We should check the key is set in the message first instead.
Change-Id: Ic4c17e96c3975adcbc49eb82e7b1999d3dcec851
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
| |
On some platforms, Designer is not located in any of the qtpaths keys
directly. We also need to check `tools/qttools/bin` for Designer.
Change-Id: I0a49868262019654d6fd8aebbc9be76fb9f3da20
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
* Send events when commands are executed
* Add https://www.npmjs.com/package/@vscode/extension-telemetry
* Update ThirdPartyNotices.txt
Task-number: VSCODEEXT-62
Change-Id: I7c88b0db55fa14da6d66025e7fa4458726f5ce6b
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove `getSelectedQtInstallationPath()` use `getSelectedKit()` instead
Since we support both root installation kits and qtpaths, we cannot just
return the installation path of the selected kit. We need to return
the all kit information.
* Use only qtpaths exe paths to cache information
Since we store only qtpaths exe paths in `cmake-kits.json`, we don't
need to hash it with other values like name or isVCPKG. And also, we can
improving the performance by caching different kits but with the same
qtpaths.
* Implement `qt-cpp.qtDir` for debug templates on Windows
We have to return possible dll paths for qtpaths kits.
* Deprecate `qt-cpp.kitDirectory` and use `qt-cpp.qtDir` instead
We support both root installation kits and qtpaths. So we cannot just
rely on `qt-cpp.kitDirectory\bin` in debug templates. For qtpaths, we
need to return multiple paths.
* Remove `kit-directory.ts` and move content to `launch-variables.ts`
* Add `qt-cpp.qpaPlatfromPluginPath`
When we debug with Qt from vcpkg. We get the
`could not find or load the Qt platform plugin "windows" in "",` error
if we don't set the `QT_QPA_PLATFORM_PLUGIN_PATH` environment variable.
That's why we need to set `qt-cpp.qpaPlatfromPluginPath` according to
`cmake.buildType` either `debug` or `release` path.
* Locate Designer via qtpaths
To support using Designer from qtpaths, we need to locate the Designer
inside paths like `QT_HOST_BINS`, `QT_HOST_LIBEXECS`,
`QT_INSTALL_LIBEXECS`
* Remove error messages when a qtpaths kit selected
In the previous implementation, we showed an error message when a
qtpaths kit selected instead of root installation kits.
* Add Qt version detection from qtpaths
* Add selectedQtPaths to coreAPI
When a qtpaths kit is selected, we set `selectedQtPaths` to inform
other extensions.
* Move `queryHostBinDirPath` to `qt-ui/util.ts`
Since it is only used in `qt-ui`, we move it to `qt-ui/util.ts`
* Shorten `locateQtDesignerExePath()` to `locateDesigner()`
* Use `set designerClient()` and detach inside it
It is better encapsulation.
Task-number: VSCODEEXT-86
Task-number: VSCODEEXT-93
Task-number: VSCODEEXT-92
Change-Id: I0aadd4dd5e2f9508576dda70d24eb14de7796a86
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
The `ProjectManager` classes in qt-core, qt-cpp are now derived from
the `ProjectManager` template class in qt-lib.
Rename `ProjectBase` to `Project` for simplcity and consistency.
Change-Id: I66492028f43eb8822e2be5cde87de8a97c214381
Reviewed-by: Orkun Tokdemir <orkun.tokdemir@qt.io>
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add tilde support for `qt-cpp.installationRoot`,
`qt-cpp.qtadditionalQtPaths`, `qt-qml.qmlls.customExePath` and
`qt-ui.customWidgetsDesignerExePath`.
* Update the `package.json` files
* Update ThirdPartyNotices.txt
Change-Id: Ieefda914b46e78882cc18dd98eef86d26399f1b8
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
| |
Change-Id: Id7b61cc70c97b3e859a0004bb206e970ca51f17e
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new configuration value can be used to specify Qt installations
that were not provided by the Qt installer. The values are absolute
paths to the qtpaths or qmake executables of a Qt installation.
For values in qt-core.additionalQtPaths we now generated CMake kits
like it was already the case for qt-core.qtInstallationRoot.
Fixes: VSCODEEXT-86
Change-Id: Id8eefe92c930546ede2639e18792fc78ba6558dd
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Reviewed-by: Orkun Tokdemir <orkun.tokdemir@qt.io>
|
| |
|
|
|
| |
Change-Id: I1e526a649de31f992d0652ccee8fb973e0ec7133
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add the `openWidgetDesigner`` command to open Qt Widget Designer.
* Scan both global and workspaceFolder `qtInstallationRoot`s.
* Show users current version to pick.
* Add missing parameter type in `getValue<T>()` in `CoreApiImpl`
* Move below function to qt-lib
`findQtInstallations()`
`isError()`
`matchesVersionPattern()`
Change-Id: Id0ed3714af32e24888fe60ed9e9191452293abed
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Change `qtFolder` name to `qtInstallationRoot`
* Change all related variables from `qtFolder` to `qtInstallationRoot`
* Move the `registerQt` command from `qt-official` to `qt-core`
* Move all `qtInstallationRoot` logic to `qt-core`
* Add `ProjectManager` and `StateManager` to `qt-core`
* Move `BaseStateManager` to `qt-lib`
* Update the documentation about the new config name
* Add common constants to `qt-lib`
* Fix typo
Change-Id: I785e2e4aa51f64b91d8fec7d2c264b42d80c9a16
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When a kit which do not have binaries is selected, `qt-ui` cannot locate
the designer binary because the binary is inside some specific kit
folders like `gcc_64` in Linux or `macos` in MacOS. `QT_HOST_BINS`
should be used to prevent that.
* Move `queryHostBinDirPath()` into `qt-lib`
* Enable `queryHostBinDirPath()` in `locateQtDesignerExePath()`
Change-Id: I5199ca56832b1372ffe7a1ee6c683b32a61089cb
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
|
|
|
| |
* Use `getQtCustomDesignerPath()` instead of `getDesignerPath()` which
is better naming
Change-Id: I2361f22213af7cdc0536b02d4079457b71683dee
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
| |
|
|
|
| |
Change-Id: I3dfc89485b9269b29266a47116a827ca219a48df
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
|
|
|
The below Extensions are created with this commit:
* qt-core
* qt-official
* qt-ui
qt-core
This extension is the core extension for the Qt extensions.
It provides the basic functionalities for the other extensions to work.
* It handles the communication between the other extensions.
* It provides the basic functionalities and common features for the other extensions.
* The all other extensions depend on this extension.
qt-ui
This extension provides the UI functionalities.
* It communicates with the `qt-core` extension to get information about the Qt Widget Designer.
* It provides syntax highlighting for `.ui` files.
qt-official
This extension has the rest of the previous monolithic extension functionalities.
It should be divided into more extensions in the future.
This commit implements:
* Common functionalities are moved from `qt-official` to `qt-core`.
* `qt-lib` is implemented as a npm module to gather the common code.
* Static analysis tools for every extension are added.
* Updated all `package.json` files to reflect the changes.
* `ci-scripts` is implemented to run the static analysis tools and tests.
* The `common` is created to gather the common code for tools.
* Extension packs are updated.
* The `ThirdPartyNotices.txt` files are generated for every extension.
* The `README.md` files are updated to reflect the changes.
* `.vscode/launch.json`, `.vscode/extensions.json`, and `.vscode/tasks.json` are updated.
Change-Id: Iac9b7e071275e92cdfbb3a47fba24d3ba8e41c89
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|