Now that we have conda installed and configured, getting epics-base is as easyĪs running: conda create -y -n epics epics-base conda config -add channels conda-forge Installing epics-base Environment creation To be able to install package from conda-forge,Īdd the conda-forge channel to your configuration. This doesn't really apply to Windows as you have to start the Anaconda Prompt to use conda. You should run: conda config -set auto_activate_base false On Linux and macOS, if you don't want conda to activate the base environment by default (and modify your PATH), To use conda, open the Anaconda Prompt from the start menu. curl -LO īash Miniconda3-latest-Linux-x86_64.sh -bp $HOME/minicondaīash Miniconda3-latest-MacOSX-x86_64.sh -bp $HOME/minicondaĭownload and run the Miniconda3 installer from. Note that bzip2 is required to run the installation. If you don't have conda already installed, here are some quick instructions. If you never used it before, I recommend starting by checking the documentation. This post assumes some basic knowledge of conda. I want to thank all the people who contributed to that conda recipe.Īll the examples of EPICS usage below come directly from the official website I'm not the original author of the epics-base feedstock. In this post, I want to share how to use EPICS Base with conda. I mentioned this was to update the conda-forge epics-base feedstock.

Both builds seem to run without further issues.I previously described how to create a Windows VM to build conda packages. The build has been tested on a macOS 13.2 machine (MacBook Pro 14' (2021, M1)) and on a macOS 10.13.6 virtual machine. The ad-hoc signing required for M1 based macOS versions is unaffected by this issue. Iirc, the PyInstaller documentation mentions some issues regarding code signing for 10.13, but since the builds aren't released on the App Store this seems to be mostly insignificant. I've also bumped the runner to use macos-latest since there don't seem to be any observable issues regarding backwards-compatibility. Here, I've used the conda-incubator/setup-miniconda action as replacement. Neither pygame nor any of the other dependencies caused any kinds of incompatibilities, so installing a Python version built against a lower SDK (10.13, in this case) restores High Sierra compatibility. Since the setup-python action installs libraries built for an macOS 11 SDK, older macOS versions (down to 10.13) weren't supported anymore.

How to use conda on mac