|
Size: 1616
Comment:
|
Size: 1714
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.) | '''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.) |
| Line 4: | Line 4: |
| EMAN2 uses an increasingly popular approach of writing all of the main compute-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. | 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 7: | Line 7: |
| * [:EMAN2/Install/BinaryInstall:Installing EMAN2 binaries] | * [[EMAN2/Install/BinaryInstall|Installing EMAN2 binaries]] |
| Line 9: | Line 10: |
| * [http://blake.bcm.tmc.edu/eman/eman2/INSTALL EMAN2's non-wiki installation instructions] (Linux) * [:COMPILE EMAN2 WINDOWS:Compile EMAN2 with Visual Studio .NET 2005 on Windows XP] * [:COMPILE EMAN2 MAC OS X:Compile EMAN2 on OS X] * [:COMPILE EMAN2 Fedora 9:Compile EMAN2 on Fedora 9: use yum to solve dependency issue] |
* [[http://blake.bcm.tmc.edu/eman/eman2/INSTALL|EMAN2's non-wiki installation instructions]] (Linux) * [[COMPILE_EMAN2_WINDOWS|Compile EMAN2 with Visual Studio .NET 2005 on Windows XP]] * [[COMPILE_EMAN2_MAC_OS_X|Compile EMAN2 on OS X]] |
| Line 14: | Line 15: |
| * [:eman2BuildFAQ:EMAN2 compilation frequent asked questions] * [:EMAN2 unittest:How do I know my EMAN2 installation or compilation is successful?] * [:Py initModule4 64:I try to run eman2 script, got error like "ImportError: ....libboost....: undefined symbol: Py_InitModule4_64", what does that mean?] |
* [[eman2BuildFAQ|EMAN2 compilation frequent asked questions]] * [[EMAN2_unittest|How do I know my EMAN2 installation or compilation is successful?]] * [[Py_initModule4_64|I try to run eman2 script, got error like "ImportError: ....libboost....: undefined symbol: Py_InitModule4_64", what does that mean?]] * [[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.]] |
Compiling and installing EMAN
Most users, even 'advanced' users should select a binary install. If the binaries don't work for you for some reason (please let us know, or if you need to write new low-level image processing functions, then you can resort to a source-based installation.)
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 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.
Binary Installation
Compiling from source and setting up a C++ development environment