Differences between revisions 11 and 13 (spanning 2 versions)
Revision 11 as of 2019-08-14 17:36:36
Size: 5633
Editor: TunayDurmaz
Comment: typos, build updates
Revision 13 as of 2019-08-20 18:49:06
Size: 6030
Editor: TunayDurmaz
Comment: table of contents
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Under Construction =
<<TableOfContents()>>
Line 8: Line 7:
  {{{   {{{#!highlight bash
Line 17: Line 16:
 {{{  {{{#!highlight bash
Line 22: Line 21:
 {{{  {{{#!highlight bash
Line 34: Line 33:
  {{{   {{{#!highlight bash
Line 38: Line 37:
  {{{   {{{#!highlight bash
Line 42: Line 41:
 {{{  {{{#!highlight bash
Line 46: Line 45:
 {{{  {{{#!highlight bash
Line 60: Line 59:
 {{{  {{{#!highlight bash
Line 64: Line 63:
 {{{  {{{#!highlight bash
Line 68: Line 67:
 {{{  {{{#!highlight bash
Line 72: Line 71:
 {{{  {{{#!highlight bash
Line 76: Line 75:
 {{{  {{{#!highlight bash
Line 82: Line 81:
 {{{  {{{#!highlight bash
Line 102: Line 101:
 {{{  {{{#!highlight bash
Line 107: Line 106:
 {{{  {{{#!highlight bash
Line 113: Line 112:
 {{{  {{{#!highlight bash
Line 120: Line 119:
 {{{  {{{#!highlight bash
Line 128: Line 127:
 {{{  {{{#!highlight bash
Line 133: Line 132:
 {{{  {{{#!highlight bash
Line 139: Line 138:
 {{{  {{{#!highlight bash
Line 146: Line 145:
 {{{  {{{#!highlight bash
Line 155: Line 154:
 {{{  {{{#!highlight bash
Line 160: Line 159:
 {{{  {{{#!highlight bash
Line 166: Line 165:
 {{{  {{{#!highlight bash
Line 173: Line 172:
 {{{  {{{#!highlight bash

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.

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

  3. Install Miniconda3.

       1 bash <Miniconda3-installer>
    
    and follow the prompts.
  4. Specify package and environment directories outside of the miniconda installation. These are the directories where conda environments and extracted packages will live. If you need to reinstall miniconda, you won't have to re-create your environments and re-download and re-extract all the packages. Reinstallation will only reset the base environment. First, create the cache directory, if it doesn't exist.

       1   mkdir -p <path-to-conda-cache-directory>
       2 # mkdir -p ~/conda-global-cache
       3 
       4   conda config --set pkgs_dirs <path-to-conda-cache-directory>/pkgs
       5 # conda config --set pkgs_dirs ~/conda-global-cache/pkgs
       6 
       7   conda config --set envs_dirs <path-to-conda-cache-directory>/envs
       8 # conda config --set pkgs_dirs ~/conda-global-cache/envs
       9 
    
  5. Configure conda.
    1. Do not update conda automatically. (Strongly recommended)

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

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

       1 conda install conda=4.6.14 -c defaults
    
  7. Initialize conda for shell interaction.
       1 conda init bash
       2 
       3 # See command help for supported shells
       4 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.
       1 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.

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

Python 3 Transition Environments

TODO

  1. Fix eman-deps versions in the PR envs.
  2. Add new env for new compilers, maybe, for boost 1.67 and update eman-deps-feedstock.

END TODO

Phase 1: Upgrade CMake to 3.14

PR: Upgrade CMake to 3.14

  1. Create a new environment and activate it.
       1 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
       2 conda activate eman-deps-14.2
    
  2. Navigate to your source directory. Checkout branch cmake-upgrade and pull updates from the remote.

       1 cd <source directory>
       2 git checkout cmake-upgrade
       3 git pull --rebase
    
  3. Navigate to your build directory, build and install.
       1 cd <build directory>
       2 cmake <eman2 source directory>
       3 make
       4 make install
    
  4. To switch to another conda environment, first deactivate your current environment.
       1 conda deactivate
    

Phase 2: Test Boost 1.64

PR: Upgrade Boost to 1.64

  1. Create a new environment and activate it.
       1 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
       2 conda activate eman-deps-14.3
    
  2. Navigate to your source directory. Checkout branch py2-boost-164 and pull updates from the remote.

       1 cd <source directory>
       2 git checkout py2-boost-164
       3 git pull --rebase
    
  3. Navigate to your build directory, build and install.
       1 cd <build directory>
       2 cmake <eman2 source directory>
       3 make
       4 make install
    
  4. To switch to another conda environment, first deactivate your current environment.
       1 conda deactivate
    

Phase 3: Test Boost 1.66

PR: Build with Boost versions 1.65-1.66

  1. Create a new environment and activate it.
       1 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
       2 conda activate eman-deps-14.3
    
  2. Navigate to your source directory. Checkout branch py2-boost-166 and pull updates from the remote.

       1 cd <source directory>
       2 git checkout py2-boost-166
       3 git pull --rebase
    
  3. Navigate to your build directory, build and install.
       1 cd <build directory>
       2 cmake <eman2 source directory>
       3 make
       4 make install
    
  4. To switch to another conda environment, first deactivate your current environment.
       1 conda deactivate