Releases: afri-bit/vsconan
v1.4.0
What's Changed
Added
- #50 Conan Package Revision directory structure
Show content of package revision in the treeview, basically recreating the file explorer for the conan package revision
Changed
- #43 Improved the UX on conan profile selection
Removed the edit button, and replace it with native VS code click interface. User can open the conan profile in the editor by double clicking / single clicking (depends on the configuration.)
Full Changelog: v1.3.2...v1.4.0
v1.3.2
v1.3.1
What's Changed
- Fix activation of BuildEnv/RunEnv by @hackenbergstefan in #46
Full Changelog: v1.3.0...v1.3.1
Contributors
Assets 2
v1.3.0
What's Changed
- Support the application of Conan's BuildEnv/RunEnv by @hackenbergstefan in #44
- Add status bar buttons for frequent operations by @hackenbergstefan in #45
Huge thanks to @hackenbergstefan for actively contributing to this project.
Full Changelog: v1.2.0...v1.3.0
Contributors
Assets 3
v1.2.0
What's Changed
Added
- Leverage ms-python.python extension to resolve python interpreter path automatically by @hackenbergstefan in #39
New Contributors
- @hackenbergstefan made their first contribution in #39
Full Changelog: v1.1.0...v1.2.0
Contributors
Assets 3
v1.1.0
Added
-
#38 Support whitespace for project and configuration path
You can now use whitespace in your configuration file and VSConan can still parse the path and use it for executing conan command.Additional to this feature, internal the command builder is changed to separate the command and arguments. For further detail of the issue please refer to #38.
This change should not affect the current configuration file.Thanks to torsknod-the-caridian.
Full Changelog: v1.0.1...v1.1.0
v1.0.1
v1.0.0
Breaking Changes
-
Following settings in
settings.jsonare OBSOLETEvsconan.general.pythonInterpretervsconan.general.conanExecutablevsconan.general.conanExecutionMode
Instead, you can define multiple profiles according to your need in the
settings.json. See example below:"vsconan.conan.profile.configurations": { "myprofile_1": { "conanVersion": "1", "conanPythonInterpreter": "python", "conanExecutable": "conan", "conanExecutionMode": "pythonInterpreter", }, "myprofile_2": { "conanVersion": "2", "conanPythonInterpreter": "/home/user/.venv/bin/conan", "conanExecutable": "/home/user/.venv/bin/conan", "conanExecutionMode": "conanExecutable", "conanUserHome": "/home/user/your/path/to/.conan2" } }, "vsconan.conan.profile.default": "myprofile_2",
Using
vsconan.conan.profile.defaultyou can switch the profile easily, in case you have multiple conan setup or multiple python virtual environments with different conan versions.conanUserHomeis optional parameter, in case you want to have a different location forconanhome folder. -
The workspace configuration to execute conan command, such as
build,install, etc., is slightly changed, but it has a big impact to your workflow / usage of this configuration.The
pythonattribute is no longer available!Instead of using hard coded
pythonpath inside this json file, it will rely on the selected conan configuration profile. So with this change, you can use the same json file but using in the different conan version (Easy switch between conan 1 and 2).{ "commandContainer": { "create": [ { "name": "create", "description": "Create command", "detail": "Create command detail", "conanRecipe": "conanfile.py", "profile": "default", "user": "", "channel": "", "args": [] } ], "install": [ { "name": "install", "description": "Install command", "detail": "Install command detail", "conanRecipe": "conanfile.py", "installFolder": "install", "profile": "default", "user": "", "channel": "", "args": [] } ], . . . . } }Due to the fact that there are some differences in the commands between conan 1 and 2, some attributes are added to some commands, that might not be used in one conan version or the other.
Following example might give you clarity.-
Conan 1 -
conan sourceoptional arguments: -h, --help -sf SOURCE_FOLDER, --source-folder SOURCE_FOLDER -if INSTALL_FOLDER, --install-folder INSTALL_FOLDER
-
Conan 2 -
conan sourceoptional arguments: --name NAME --version VERSION --user USER --channel CHANNEL
-
Added
- Conan 2 - Browsing the recipe with UI
- Delete recipe
- Open in VSCode
- Open in explorer
- Conan 2 - Browsing the packages with UI
- Delete Package
- Open in VSCode
- Open in explorer
- Conan 2 - Browsing the package revisions with UI
- Delete package revision
- Open in VSCode
- Open in explorer
- Conan 2 - Working with remotes with tree view
- Same functionality as conan1
- Conan 2 - Working with profiles with Tree view
- Same functionality as conan1
- Multiple profile definition for conan configuration in
settings.json - Easy switch between conan configuration profile using status bar
- Status bar view of selected conan configuration profile
- Added new treeview for package revision (Only meant for conan2)
Changed
- New color palette for the VSConan logo :) Adapted the color according to the new official conan logo (roughly)
v0.4.0
Added
- #24 Open different folders under recipe folder
- User has the possibility to access different folders that are located under the recipe folder itself, such as
build,dl,source, etc. - User can open the folder either in the explorer or in a new VS Code window. The option to open the folders can be found by using right click on the recipe item from the explorer.
- User has the possibility to access different folders that are located under the recipe folder itself, such as
- #17 Filter recipes based on a selected remote
- #18 Filter binary packages based on a selected remote
v0.3.0
Added
- #16 Configuration in settings.json for
CONAN_USER_HOME- Enable possibility to overwrite the pre defined
CONAN_USER_HOMEenvironment variable usingvsconan.general.conanUserHomeconfiguration option - User can set home directory to conan local cache within the VS Code using
settings.jsonfile
- Enable possibility to overwrite the pre defined