{"action":"closed","issue":{"url":"https://api.github.com/repos/conda/conda/issues/2901","repository_url":"https://api.github.com/repos/conda/conda","labels_url":"https://api.github.com/repos/conda/conda/issues/2901/labels{/name}","comments_url":"https://api.github.com/repos/conda/conda/issues/2901/comments","events_url":"https://api.github.com/repos/conda/conda/issues/2901/events","html_url":"https://github.com/conda/conda/issues/2901","id":162738002,"number":2901,"title":"Add \"build.d\" analogous to \"activate.d\" to activate script to support compiler configurations","user":{"login":"mwiebe","id":399551,"avatar_url":"https://avatars3.githubusercontent.com/u/399551?v=3","gravatar_id":"","url":"https://api.github.com/users/mwiebe","html_url":"https://github.com/mwiebe","followers_url":"https://api.github.com/users/mwiebe/followers","following_url":"https://api.github.com/users/mwiebe/following{/other_user}","gists_url":"https://api.github.com/users/mwiebe/gists{/gist_id}","starred_url":"https://api.github.com/users/mwiebe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mwiebe/subscriptions","organizations_url":"https://api.github.com/users/mwiebe/orgs","repos_url":"https://api.github.com/users/mwiebe/repos","events_url":"https://api.github.com/users/mwiebe/events{/privacy}","received_events_url":"https://api.github.com/users/mwiebe/received_events","type":"User","site_admin":false},"labels":[{"id":16544532,"url":"https://api.github.com/repos/conda/conda/labels/type:feature","name":"type:feature","color":"e99695","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-06-28T17:10:51Z","updated_at":"2017-05-10T02:16:09Z","closed_at":"2017-05-10T02:16:09Z","body":"I'm putting this feature proposal here instead of in `conda build`, because I think it could be structured here generically as a support mechanism that both `conda build` and other build systems using conda could utilize.\n\nThe idea is to do two things:\n1. Add `$PREFIX/etc/conda/build.d` which is shell scripts or batch files which are sourced on activation in package building/development mode.\n2. Add `-b` option to `activate`, so `$ source activate -b mydevenv` would source both `activate.d` scripts and `build.d` scripts.\n\nWith this mechanism in place, `conda build` can fully remove its hardcoded knowledge about Python versions <-> compiler settings, and recipes designed to work with multiple compiler settings can be written generically instead of having to do a `source compiler_config.sh` as described in https://github.com/conda/conda-build/issues/911. Basically, `conda build` would no longer call the MSVC `vcvars.bat` file, it would instead use `source activate -b _build` instead of `source activate _build`, so that the compiler setup would happen in a `build.d` file.\n\nTo keep Anaconda working the same, the `python` package could add a file to `build.d` which replicates the current behaviour. It would be nicer in my opinion for there to be a different metapackage for this purpose, that depend on the installed `python`, so that it would be possible to have `python` installed for scripting use without polluting the build environment. That would seem to require changing Anaconda and establishing new conventions for python recipes that build C/C++ extensions.\n"}}
{"actor":{"display_login":"kalefranz"}}