{"action":"created","issue":{"url":"https://api.github.com/repos/conda/conda-build/issues/3007","repository_url":"https://api.github.com/repos/conda/conda-build","labels_url":"https://api.github.com/repos/conda/conda-build/issues/3007/labels{/name}","comments_url":"https://api.github.com/repos/conda/conda-build/issues/3007/comments","events_url":"https://api.github.com/repos/conda/conda-build/issues/3007/events","html_url":"https://github.com/conda/conda-build/issues/3007","id":340459185,"node_id":"MDU6SXNzdWUzNDA0NTkxODU=","number":3007,"title":"conda build fails for Visual Studio 2017 (where it works for Visual Studio 2015)","user":{"login":"0zeroth","id":8716660,"node_id":"MDQ6VXNlcjg3MTY2NjA=","avatar_url":"https://avatars0.githubusercontent.com/u/8716660?v=4","gravatar_id":"","url":"https://api.github.com/users/0zeroth","html_url":"https://github.com/0zeroth","followers_url":"https://api.github.com/users/0zeroth/followers","following_url":"https://api.github.com/users/0zeroth/following{/other_user}","gists_url":"https://api.github.com/users/0zeroth/gists{/gist_id}","starred_url":"https://api.github.com/users/0zeroth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/0zeroth/subscriptions","organizations_url":"https://api.github.com/users/0zeroth/orgs","repos_url":"https://api.github.com/users/0zeroth/repos","events_url":"https://api.github.com/users/0zeroth/events{/privacy}","received_events_url":"https://api.github.com/users/0zeroth/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-12T01:33:10Z","updated_at":"2018-07-12T02:17:52Z","closed_at":null,"author_association":"NONE","body":"A working Visual Studio 2017 installation (eg Cython works and automagically finds the compiler) will not work with `conda build` (it will complain it can't find a compiler)\r\n\r\nThe work-around is to either install Visual Studio 2015 _or_ run `conda build` from inside the Visual Studio command prompt.\r\n"},"comment":{"url":"https://api.github.com/repos/conda/conda-build/issues/comments/404367986","html_url":"https://github.com/conda/conda-build/issues/3007#issuecomment-404367986","issue_url":"https://api.github.com/repos/conda/conda-build/issues/3007","id":404367986,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNDM2Nzk4Ng==","user":{"login":"msarahan","id":38393,"node_id":"MDQ6VXNlcjM4Mzkz","avatar_url":"https://avatars3.githubusercontent.com/u/38393?v=4","gravatar_id":"","url":"https://api.github.com/users/msarahan","html_url":"https://github.com/msarahan","followers_url":"https://api.github.com/users/msarahan/followers","following_url":"https://api.github.com/users/msarahan/following{/other_user}","gists_url":"https://api.github.com/users/msarahan/gists{/gist_id}","starred_url":"https://api.github.com/users/msarahan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msarahan/subscriptions","organizations_url":"https://api.github.com/users/msarahan/orgs","repos_url":"https://api.github.com/users/msarahan/repos","events_url":"https://api.github.com/users/msarahan/events{/privacy}","received_events_url":"https://api.github.com/users/msarahan/received_events","type":"User","site_admin":false},"created_at":"2018-07-12T02:17:52Z","updated_at":"2018-07-12T02:17:52Z","author_association":"CONTRIBUTOR","body":"conda-build is set up to be compiler-agnostic.  Any compiler \"magic\" is legacy and no longer actively supported.  All compiler configuration should be done with compiler packages.  An example VS2017 recipe for compiler package is at https://github.com/AnacondaRecipes/aggregate/tree/master/vs2017\r\n\r\nYou'd then need to specify the compiler as vs2017 in a conda_build_config.yaml file, because the default version is otherwise 2015 for python 3.5+.  Please see https://conda.io/docs/user-guide/tasks/build-packages/compiler-tools.html and https://github.com/AnacondaRecipes/aggregate/blob/master/conda_build_config.yaml#L21\r\n\r\nThis is not supported (let alone default) yet because we have not yet begun using VS2017 ourselves.  There have been numerous showstopping bugs with VS2017 and we're waiting for an adequate release."}}
{"actor":{"display_login":"msarahan"}}