Adds an example of using toolchains to resolve multiple environments.#28
Adds an example of using toolchains to resolve multiple environments.#28jiawen wants to merge 1 commit into
Conversation
|
Related: #28. Turns out we don't need platforms. |
| # The name argument is required because `register_toolchain` constructs a single external repository | ||
| # and writes a BUILD file into it. | ||
| register_toolchain( | ||
| name = "test2", |
There was a problem hiding this comment.
This is ok but might be irritating to use - because the rule makes a single BUILD file. Maybe add an extra register_toolchains function that lets you pass in multiple envs and names?
There was a problem hiding this comment.
First thought: We can name it after the environment name, like test2_env_toolchain. That way only the environment name would be needed.
Second thought: One function that registers all toolchains might be better to enforce correctness and even maybe more user-friendly. Depends on how exactly the arguments will be passed.
|
@spietras Any idea what's going on with the Windows test? I haven't touched Anaconda on Windows in a long time but AFAICT, I'm not doing anything obviously wrong. |
|
@jiawen The first thing I would try is to increase the CACHE_NUMBER in the github workflow, to try to fix what looks like a corrupted cache maybe. Do you have a Windows workstation on hand to test with locally? |
Surprisingly yes :). Let me give that a shot. I know nothing about GitHub workflows - time to learn I guess. 🤷 |
|
Yet another possibility might be because of the |
3 participants
No description provided.