Differences between revisions 6 and 7
Revision 6 as of 2019-07-11 05:39:40
Size: 3845
Editor: TunayDurmaz
Comment: Python 3 Transition Environments
Revision 7 as of 2019-07-12 04:41:39
Size: 4070
Editor: TunayDurmaz
Comment: Some improvements
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

Line 7: Line 9:
mkdir -p <path-to-conda-cahe-directory>   mkdir -p <path-to-conda-cahe-directory>
Line 9: Line 11:
Line 18: Line 21:
 1. Specify package and environment directories.  1. Specify package and environment directories. These are the directories where conda environments and extracted packages will live.
Line 20: Line 23:
conda config --set pkgs_dirs <path-to-conda-cahe-directory>/pkgs   conda config --set pkgs_dirs <path-to-conda-cahe-directory>/pkgs
Line 22: Line 25:
conda config --set envs_dirs <path-to-conda-cahe-directory>/envs
  
conda config --set envs_dirs <path-to-conda-cahe-directory>/envs
Line 26: Line 30:
  a. Do not update conda automatically.   a. Do not update conda automatically. '''(Strongly recommended.)'''
Line 30: Line 34:
  a. If you don't want conda's base environment to be activated automatically.   a. If you don't want conda's base environment to be activated automatically. '''(Optional)'''
Line 41: Line 45:
Line 45: Line 50:
== Use Conda Environments for Development ==
Do not install anything into the base environment, do not use the base environment for development, use non-base environments.


== Development Environments ==

Do not install anything into the '''base''' environment, do not use the '''base''' environment for development, use '''non-base''' environments.
Line 64: Line 72:
 1. Checkout a branch.
 1. Update eman2 source.
 1. Navigate to your source directory. Checkout a branch and pull updates from the remote.
Line 83: Line 90:
== CMake 3.14 ==
== Upgrade CMake to 3.14 ==
Line 96: Line 104:
== Boost 1.64 == == Test Boost 1.64 ==
Line 109: Line 117:
== Boost 1.66 ==
== Test Boost 1.66 ==

Under Construction

Setup Development Environment with Conda

  1. If you have an existing Miniconda2 installation,

    1. Remove miniconda entries from PATH.

    2. If you want to make use of your cached packages, move your pkgs/ and envs/ folders out of your current installation to another location.

        mkdir -p <path-to-conda-cahe-directory>
      # mkdir -p ~/conda-global-cache
      
      mv <path-to-current-miniconda2-installation>/pkgs <path-to-conda-cahe-directory>
      mv <path-to-current-miniconda2-installation>/envs <path-to-conda-cahe-directory>
  2. Download Miniconda3 for Linux or MacOSX.

  3. Install Miniconda3.

    bash <Miniconda3-installer>
    • and follow the prompts.
  4. Specify package and environment directories. These are the directories where conda environments and extracted packages will live.
      conda config --set pkgs_dirs <path-to-conda-cahe-directory>/pkgs
    # conda config --set pkgs_dirs ~/conda-global-cache/pkgs
    
      conda config --set envs_dirs <path-to-conda-cahe-directory>/envs
    # conda config --set pkgs_dirs ~/conda-global-cache/envs
  5. Configure conda.
    1. Do not update conda automatically. (Strongly recommended.)

      conda config --set auto_update_conda False
    2. If you don't want conda's base environment to be activated automatically. (Optional)

      conda config --set auto_activate_base False
  6. Install conda 4.6.14.

    conda install conda=4.6.14 -c defaults
  7. Initialize conda for shell interaction.
    conda init bash
    
    # See command help for supported shells
    conda init --help

Development Environments

Do not install anything into the base environment, do not use the base environment for development, use non-base environments.

  1. Create a new environment.
    conda create -n eman-deps-14.1 eman-deps=14.1 -c cryoem -c defaults -c conda-forge

    OR choose a simpler name for the environment, eman-env or eman.

    conda create -n eman-env eman-deps=14.1 -c cryoem -c defaults -c conda-forge
  2. Activate the environment.
    conda activate eman-deps-14.1
    OR
    conda activate eman-env
  3. Navigate to your source directory. Checkout a branch and pull updates from the remote.
    cd <source directory>
    git checkout <branch>
    git pull --rebase
  4. Navigate to your build directory, build and install.
    cd <build directory>
    cmake <eman2 source directory>
    make
    make install

Python 3 Transition Environments

Upgrade CMake to 3.14

PR: Upgrade CMake to 3.14

  1. Create a new environment and activate it.
    conda create -n eman-deps-14.2 eman-deps=14.2 cmake=3.14 -c cryoem/label/dev -c cryoem -c defaults -c conda-forge
    conda activate eman-deps-14.2
  2. To switch to another conda environment, first deactivate your current environment.
    conda deactivate

Test Boost 1.64

PR: Upgrade Boost to 1.64

  1. Create a new environment and activate it.
    conda create -n eman-deps-14.2 eman-deps=14.3 cmake=3.14 boost=1.64 -c cryoem/label/boost -c cryoem -c defaults -c conda-forge
    conda activate eman-deps-14.3
  2. To switch to another conda environment, first deactivate your current environment.
    conda deactivate

Test Boost 1.66

PR: Build with Boost versions 1.65-1.66

  1. Create a new environment and activate it.
    conda create -n eman-deps-14.2 eman-deps=14.3 cmake=3.14 boost=1.66 -c cryoem/label/boost -c cryoem -c defaults -c conda-forge
    conda activate eman-deps-14.3
  2. To switch to another conda environment, first deactivate your current environment.
    conda deactivate