Differences between revisions 28 and 38 (spanning 10 versions)
Revision 28 as of 2017-06-09 19:22:01
Size: 1577
Editor: TunayDurmaz
Comment:
Revision 38 as of 2017-06-14 22:04:21
Size: 2011
Editor: TunayDurmaz
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

The following instructions will work with cmake changes introduced in https://github.com/cryoem/eman2/pull/65.
Line 17: Line 15:
 1. Optionally, activate an existing conda environment, e.g. `source activate eman-env`. Skip this step, if you don't understand this statement.  1. Optionally, activate an existing conda environment, e.g. `source activate eman-env`. Skip this step, if you don't understand this statement. However, if you already use anaconda, you may get package conflicts when you install eman dependencies in the next step. In that case, you need to install eman and its dependencies in its own conda environment and skip the next step, "Install dependencies".{{{
conda create -n eman-env eman-deps -c cryoem -c defaults -c conda-forge
source activate eman-env
}}}
Line 26: Line 27:
export MACOSX_DEPLOYMENT_TARGET=10.7 # only for MacOSX
cmake <some-path-to-keep-eman2-source> -DENABLE_CONDA=ON
rm -f CMakeCache.txt # This is needed to ensure cmake doesn't have any leftovers from previous runs
cmake <some-path-to-keep-eman2-source> -DENABLE_CONDA=ON \
                                       -DEMAN_CXX_FLAGS="-D_GLIBCXX_USE_CXX11_ABI=0" # This flag will be set in cmake with https://github.com/cryoem/eman2/pull/80
Line 32: Line 34:


== Windows ==

!!! UNDER CONSTRUCTION !!!

All platforms

Mac OS X, Linux

  1. Download and install Anaconda2 or Miniconda2.

  2. Checkout EMAN2 code from GitHub:cryoem/eman2.

    cd <some-path-to-keep-eman2-source>
    git clone https://github.com/cryoem/eman2.git
  3. Optionally, activate an existing conda environment, e.g. source activate eman-env. Skip this step, if you don't understand this statement. However, if you already use anaconda, you may get package conflicts when you install eman dependencies in the next step. In that case, you need to install eman and its dependencies in its own conda environment and skip the next step, "Install dependencies".

    conda create -n eman-env eman-deps -c cryoem -c defaults -c conda-forge
    source activate eman-env
  4. Install dependencies

    conda install eman-deps -c cryoem -c defaults -c conda-forge

    Listing the channels explicitly can be avoided by specifying them in $HOME/.condarc, see conda documentation for more details, https://conda.io/docs/using/index.html.

  5. Out-of-source builds are recommended, so work in a directory outside of eman2 source (this is generally true, not EMAN2-specific). Note cmake, not ccmake . CMake will automatically find the dependencies. If you want to change any of the CMake values, then use cmake-gui or ccmake.

    cd <build-directory>
    rm -f CMakeCache.txt  # This is needed to ensure cmake doesn't have any leftovers from previous runs
    cmake <some-path-to-keep-eman2-source> -DENABLE_CONDA=ON \
                                           -DEMAN_CXX_FLAGS="-D_GLIBCXX_USE_CXX11_ABI=0"  # This flag will be set in cmake with https://github.com/cryoem/eman2/pull/80
    make -j           # "make" should pick up the number of available processors,
    make -j4          # but you may specify the number if you like
    make install

EMAN2/COMPILE_EMAN2_ANACONDA-PRE-CONDA-ENVIRONMENTS (last edited 2019-11-01 14:27:54 by TunayDurmaz)