Closed jgsogo closed 8 months ago
We already have a conan.config.json file we can use to add custom commands to the extension. The user would be able to:
conan.config.json
install
$(conan)
$(install-path)
$(conanfile)
<project-pattern>::<configuration>
{ "commands": { "<project-pattern>::configuration": { "My command": "do wathever thing", "Other command": "do wathever thing" }, "ThisProject::Release|Win32": { "install": "$(conan) config install $(conanfile) -r myremote", "My command": "different for this project" } } }
The UI should be quite straightforward using the context menu:
[Project (right click)] +-- Install (Current project) // This will run the `install` command +-- Conan +-- My command +-- Other command
The main problem I can think about is that we should recreate the menus with every configuration change, although it might not be a bid deal.
wdyt?
We already have a
conan.config.json
file we can use to add custom commands to the extension. The user would be able to:install
command per project-configuration$(conan)
,$(install-path)
,$(conanfile)
,...<project-pattern>::<configuration>
(order matters!)The UI should be quite straightforward using the context menu:
The main problem I can think about is that we should recreate the menus with every configuration change, although it might not be a bid deal.
wdyt?