|
Size: 2986
Comment:
|
Size: 1976
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| '''Most users, even 'advanced' users should select a binary install.''' If the binaries don't work for you for some reason (please [[mailto:sludtke@bcm.edu|let us know]], or if you need to write new low-level image processing functions, then you can resort to a source-based installation.) | The new EMAN2.2 binaries for recent OS versions are more heavily optimized than previous releases (and less backwards compatible). Still, it may be possible to achieve a 10-20% additional speedup if you setup GCC6 and compile with optimize-machine on a recent Linux version. Compiling from source on Linux is much easier than the other platforms. For Mac and Windows users, we strongly suggest using a binary. |
| Line 5: | Line 5: |
EMAN2 uses an increasingly popular approach of writing all of the main computationally intensive image processing operations in C++, but writing all of the user programs, including those with GUIs (graphical user interfaces) in a scripting language called [[http://www.python.org|Python]]. All of these Python level programs can be edited by the end-user WITHOUT requiring a C++ development environment. Note that most users won't want or need even this level of customization. |
|
| Line 14: | Line 12: |
| * [[EMAN2/COMPILE_EMAN2_MAC_OS_X|Compile EMAN2 on OS X]] * [[EMAN2/BREW_EMAN2_MAC_OS_X|Compile EMAN2 on OS X with Homebrew]] |
|
| Line 17: | Line 13: |
| * [[EMAN2/COMPILE_EMAN2_WINDOWS|Compile EMAN2 with Visual Studio .NET 2005 on Windows XP]] | * [[EMAN2/COMPILE_EMAN2_MAC_OS_X|Compile EMAN2 on OS X with Anaconda]] (recommended) * [[EMAN2/BREW_EMAN2_MAC_OS_X|Compile EMAN2 on OS X with Homebrew]] (not recommended) |
| Line 19: | Line 16: |
| * [[EMAN2/ExternalLibraries|External libraries needed for EMAN2 compilation]] | * [[EMAN2/COMPILE_EMAN2_WINDOWS|Compile EMAN2 with Visual Studio .NET 2005 on Windows XP (OBSOLETE)]] |
| Line 25: | Line 22: |
| * [[EMAN2/FAQ/Py_initModule4_64|I try to run eman2 script, got error like "ImportError: ....libboost....: undefined symbol: Py_InitModule4_64", what does that mean?]] * [[EMAN2/FAQ/EMAN2Mandriva2009Segfault|I compiled EMAN2 on Mandriva 2009, everything looks OK, but I got segmentation fault when I try to run e2display.py or e2boxer.py.]] |
|
| Line 30: | Line 25: |
| * [[EMAN2/FAQ/UseEman2_Ubuntu|EMAN2 installed under Ubuntu 8.04 Linux doesn't work properly. Any suggestions?]] * [[EMAN2/FAQ/Ubuntu_8.10_error_running_e2.py|Ubuntu 8.10 error running e2.py]] * [[EMAN2/FAQ/OpenSuSE_11.1|EMAN2 installed on OpenSuSE got "symbol lookup error"]] |
Installing EMAN2
The new EMAN2.2 binaries for recent OS versions are more heavily optimized than previous releases (and less backwards compatible). Still, it may be possible to achieve a 10-20% additional speedup if you setup GCC6 and compile with optimize-machine on a recent Linux version. Compiling from source on Linux is much easier than the other platforms. For Mac and Windows users, we strongly suggest using a binary.
Binary Installation (most users should do this)
Compiling from Source and Setting Up a C++ Development Environment
To get EMAN2 source, please go to GitHub: http://github.com/cryoem/eman2
Compile EMAN2 on Linux | EMAN2's non-wiki installation instructions
Compile EMAN2 on OS X with Anaconda (recommended)
Compile EMAN2 on OS X with Homebrew (not recommended)
Compile EMAN2 with Visual Studio .NET 2005 on Windows XP (OBSOLETE)
FAQ
How do I know my EMAN2 installation or compilation is successful?
Does EMAN2 support Internationalization/other language conventions ?
Why is EMAN2 distributed as an 'EMAN2' directory rather than Linux RPM's, etc. ?
EMAN2 installed under OSX doesn't work properly. Any suggestions?
EMAN2 installed under Windows doesn't work properly. Any suggestions?
