You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just realized that this logic doesn't properly handle consumers running conan from a bash terminal on Windows and setting tools.microsoft.bash:active=True (this conf didn't exist AFAIK when we have implemented this logic in conancenter recipes) and tools.microsoft.bash:subsystem. Indeed in this case tools.microsoft.bash:path is useless and not used at all in conan v2 client, so there is no reason for consumers to set this conf.
But if tools.microsoft.bash:path is not set, current conancenter recipes will download msys2 recipe and inject it in build context (and override conf of users?) while it's useless and could even lead to conflicts and weird behavior.
What is your question?
Currently in conan v2 recipes, we have this logic in build requirements when a bash is needed and build machine is Windows:
I just realized that this logic doesn't properly handle consumers running conan from a bash terminal on Windows and setting
tools.microsoft.bash:active=True
(this conf didn't exist AFAIK when we have implemented this logic in conancenter recipes) andtools.microsoft.bash:subsystem
. Indeed in this casetools.microsoft.bash:path
is useless and not used at all in conan v2 client, so there is no reason for consumers to set this conf.But if
tools.microsoft.bash:path
is not set, current conancenter recipes will download msys2 recipe and inject it in build context (and override conf of users?) while it's useless and could even lead to conflicts and weird behavior.So I guess we could replace this logic by:
@memsharded what do you think?
or maybe more explicit?
The text was updated successfully, but these errors were encountered: