conan-vs-extension
conan-vs-extension copied to clipboard
Manage remotes
add dialog page to the conan options to manage remotes:
- list remotes
- add remotes
- remove remotes
- allow to specify remote for
conan install
I was tempted by this idea several times also. However, I came to believe these are actually the kinds of features that we should leave out of the extension for a long time, and possibly forever. I think they will become very time-consuming and difficult to support long-term, especially given the limited resources we have. I think we should leave GUI menus for any non-essential Conan operations out of scope. (I mean essential for visual studio project integration). I would like to build a systray-based application someday for that, but that's another topic.
I'd just like to be able to specify a -r
option to the conan command via the extension. Otherwise in some cases I'm better off running conan install
manually first to save time if I have binaries in my own remote that aren't in conan-center.
Hi! This issue has raised also for the CLion plugin (private messages). I'm wondering if these plugins/extensions should add some kind of proxy to Conan configuration (remotes, some typical config vars,...). And it always arises the alternative of having a different window to configure Conan (systray, exec, server,...) so it can we the same for VS, CLion, cmd,... but it wouldn't have a native UX. I'm on the fence with this, IMHO I think it is easy enough 😕
@jdee, for your request, there are two approaches I can think about:
-
adding an "install args" to configuration, like the CLion plugin does, but it is something that would apply to every project.
-
Using something like this approach (https://github.com/conan-io/conan-vs-extension/issues/171) to override the
install
command