{"action":"opened","issue":{"url":"https://api.github.com/repos/SciTools/conda-build-all/issues/65","repository_url":"https://api.github.com/repos/SciTools/conda-build-all","labels_url":"https://api.github.com/repos/SciTools/conda-build-all/issues/65/labels{/name}","comments_url":"https://api.github.com/repos/SciTools/conda-build-all/issues/65/comments","events_url":"https://api.github.com/repos/SciTools/conda-build-all/issues/65/events","html_url":"https://github.com/SciTools/conda-build-all/issues/65","id":177256540,"number":65,"title":"Windows VC matrix","user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars.githubusercontent.com/u/3019665?v=3","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-15T18:44:34Z","updated_at":"2016-09-15T18:44:34Z","closed_at":null,"body":"While we have discussed this several places before, wasn't seeing this tracked anywhere. So thought it best to open an issue here. Guessing we will need to handle VC correctly here before we can address it in `conda-smithy`.\r\n\r\nCurrently in order to get a package to build with multiple VC runtimes, we need to add `python` as a `build` dependency and track a feature. However, this has proved impractical and in some cases limiting. Instead discussion over the past several months has concluded the best way forward is to have a separate `vc` package for tracking the compiler that `python` and other packages track. Though ultimately this must be addressed with some kind of matrix. While we can find somewhat effective ways to do this manually, `conda-build-all` has reigned supreme at helping convert an implicit matrix to an explicit matrix (via leveraging by `conda-smithy`). Hence I'm raising this here to ask that `vc` be handled in the matrix configuration used by `staged-recipes` and can picked up with `conda-smithy` for use in the feedstocks. There are already some considerations about how this [might play out]( https://github.com/conda-forge/tk-feedstock/pull/2#issuecomment-235782005 ).\r\n\r\nxref: https://github.com/conda-forge/glpk-feedstock/pull/10\r\nxref: https://github.com/conda-forge/tk-feedstock/pull/2\r\nxref: https://github.com/conda-forge/conda-smithy/issues/245\r\n\r\ncc @msarahan"}}
{"actor":{"display_login":"jakirkham"}}