Conda environment file for macOS #1141
Replies: 5 comments
-
I think we have some different options, but it would be critical to me that this environment file is somehow tested. Do you have anything creative ideas on this? |
Beta Was this translation helpful? Give feedback.
-
Yes - I think you should be able to continue sending the Linux builds and testing to Azure, and we can leverage something like this for the macOS builds, using GitHub's built in workflows. |
Beta Was this translation helpful? Give feedback.
-
Do you think we could add it to the Azure Devops pipeline (https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml) to not introduce two different build systems? |
Beta Was this translation helpful? Give feedback.
-
Absolutely - if MS is okay with us using the macOS machines for this, I am more than happy to use that system in parallel. Hopefully having a reduced set of tests for macOS helps. Let me take a stab at this and see how far I get. |
Beta Was this translation helpful? Give feedback.
-
Yeah, lets go with that. |
Beta Was this translation helpful? Give feedback.
-
As I've been getting Gadgetron building on macOS, there are different requirements for macOS on Conda, versus Linux.
The most prominent ones are the swapping of Clang for gcc, as the version of gcc available for macOS on anaconda.org is 4.8.5 versus 12.1.0 for all other platforms, and the non-existence of CUDA support libraries for macOS.
I tried if the platform-specific flags used in the gadgetron-conda-recipes repository (like here) would work in an environment creation file, but they don't seem to.
Are we okay with just adding an environment-macos.yml file right along side Gadgetron's default environment.yml file? If not - what are alternatives?
Beta Was this translation helpful? Give feedback.
All reactions