Differences between revisions 19 and 31 (spanning 12 versions)

!!! UNDER CONSTRUCTION !!!

All platforms

The following instructions will work with cmake changes introduced in https://github.com/cryoem/eman2/pull/65.

Mac OS X, Linux

Download and install Anaconda2 or Miniconda2.

Checkout EMAN2 code from GitHub:cryoem/eman2.

cd <some-path-to-keep-eman2-source>
git clone https://github.com/cryoem/eman2.git

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.
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.
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>
cmake <some-path-to-keep-eman2-source> -DENABLE_CONDA=ON
make -j           # "make" should pick up the number of available processors,
make -j4          # but you may specify the number if you like
make install
```

Windows

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

-  ⇤ ← Revision 19 as of 2017-06-09 04:03:17 → 
  Size: 1244
  Editor: TunayDurmaz
  Comment:
+   ← Revision 31 as of 2017-06-11 21:28:28 → ⇥
  Size: 1721
  Editor: TunayDurmaz
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 17:
-. Optionally, activate an existing conda environment, e.g. `source activate eman-env`. Skip this step if you don't understand this statement.
+. 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.
 Line 20:
-export MACOSX_DEPLOYMENT_TARGET=10.7  # only for MacOSX (Yosemite, El Capitan)
-Line 22:
+Line 21:
-}}}
+}}} 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.
-Line 24:
+Line 23:
-. 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 )--'''. {{{
+. 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'''. {{{
-Line 27:
+Line 26:
-cmake <some-path-to-keep-eman2-source>
make -j  # make should pick the number of available processors,
make -j4 # but you may specify the number if you like
+cmake <some-path-to-keep-eman2-source> -DENABLE_CONDA=ON
make -j           # "make" should pick up the number of available processors,
make -j4          # but you may specify the number if you like