search

conan-io / conan-vs-extension

Conan Extension for Visual Studio
https://marketplace.visualstudio.com/items?itemName=conan-io.conan-vs-extension
MIT License
59 stars 34 forks source link

Can't use environment variables in options for paths #138

Closed Gernatch closed 5 months ago

Gernatch commented 5 years ago

Causes "install" to do nothing: image

This is probably more of an enhancement request. Not sure if it was designed to allow environment variables.

SSE4 commented 5 years ago

yeah, that's an enhancement, right now it doesn't support any environment variables

jgsogo commented 5 years ago

We may add a configuration.Evaluate call on this path like we did in #134 for the install path, it should be quite straightforward.

SSE4 commented 5 years ago

@Gernatch to clarify - do you want Visual Studio macro definitions, like ${projectDir}, ${outDir}, etc (full list), or system environment variables, like $PATH, $TEMP, etc?

jgsogo commented 5 years ago

Hi! I see a problem with this. In the next release we are validating the path to the Conan executable. If it depends on a VS macro or environment variable, this validation doesn't make sense: the environment may change and VS macros should be evaluated per configuration.

I really like to validate the path to conan.exe in the Options menu, we guarantee that it is going to be the same for all projects and configurations, but if the motivation to allow env/macros is strong enough I can change my mind.