|
Size: 494
Comment:
|
Size: 2930
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| ''If you are not sure your Linux is 32 bit or 64 bit, you can type "uname -m -p". If it print out x86_64, it is a 64 bit machine. Or it print out i686, i386 etc., it is a 32 bit machine. '' | |
| Line 6: | Line 7: |
| ''On Linux or SGI platform, after you untar the binary package, it will create a directory called "EMAN", you have to run eman-installer script in this directory and follow the output instruction. This eman-installer is a shell script which will create a shell script to setup the corresponding environment variables for you. '' | |
| Line 7: | Line 9: |
| ==== Compiling from Source ==== '''''Under Construction ''''' |
''We limit the external library dependecy by linking them statically as much as we can. S''o you don't need those external libraries to run EMAN1, i.e. boost_python, gsl, fftw, etc.. '''''Compile from source''''' '''1. [[EMAN_COMPILE_UNIX|Compile EMAN on UNIX like systems(Linux, SGI etc.).]]''' 2. [[EMAN_COMPILE_WINDOWS|Compile EMAN on Windows XP with visual C++ 2003]]. 3. [[EMAN_COMPILE_STATIC|Semi-statically build EMAN on 64 bit Linux(x86_64).]] 4. [[EMAN_COMPILE_Ubuntu7.04|Compile EMAN on Ubuntu 7.04, 7.10, 8.04.]] 5. [[EMAN_COMPILE_MacOS_X|Compile EMAN on OS X to use on your own machine.]] *new* 6. [[EMAN_COMPILE_MacOS_X_for_Distribution|Compile EMAN on OS X and package for distribution.]] *new* '''Environement Variable Setting For EMAN''' We need set up environment variables like PATH, LD_LIBRARY_PATH and PYTHONPATH for EMAN to working correctly. These environment variables will be automatically set when you run eman-installer script when you install binary EMAN release. But for people compile from source and other diagnosis purpose, user may want to know how those environment variables should be set. 1. For sh/bash like shells on Linux/UNIX system (suppose you install EMAN under your home directory): {{{ export EMANDIR=${HOME}/EMAN export PATH=${PATH}:${EMANDIR}/bin export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${EMANDIR}/lib export PYTHONPATH=${PYTHON_PATH}:${EMANDIR}/lib }}} 2. For csh/tcsh like shell on Linux/UNIX system (suppose you install EMAN under your home directory): {{{ setenv EMANDIR ${HOME}/EMAN setenv PATH ${PATH}:${EMANDIR}/bin setenv LD_LIBRARY_PATH ${EMANDIR}/lib setenv PYTHONPATH ${EMANDIR}/lib }}} 3. For windows system (suppose you install EMAN under C:\): {{{ right click "my computer"->properties->Advanced->Environment Variables, edit the "path" entry, -> then add the EMAN's bin and lib directory into it. Add PYTHONPATH to EMAN's lib directory. }}} |
EMAN1 Installation and Tips
Binary Packages
We provide EMAN1 binary packages on several platforms: Linux(x86), Linux(x86_64), SGI(Irix6.5), Win32, Mac OS X. For Linux copy, there are stand alone version and cluster version. For 32 bit Linux platform, Linux(x86), there is a athlon version which is for athlon based machine. This athlon version linked with a athtlon optimized fftw library, fftw-gel.
If you are not sure your Linux is 32 bit or 64 bit, you can type "uname -m -p". If it print out x86_64, it is a 64 bit machine. Or it print out i686, i386 etc., it is a 32 bit machine.
On Linux or SGI platform, after you untar the binary package, it will create a directory called "EMAN", you have to run eman-installer script in this directory and follow the output instruction. This eman-installer is a shell script which will create a shell script to setup the corresponding environment variables for you.
We limit the external library dependecy by linking them statically as much as we can. So you don't need those external libraries to run EMAN1, i.e. boost_python, gsl, fftw, etc..
Compile from source
1. Compile EMAN on UNIX like systems(Linux, SGI etc.).
2. Compile EMAN on Windows XP with visual C++ 2003.
3. Semi-statically build EMAN on 64 bit Linux(x86_64).
4. Compile EMAN on Ubuntu 7.04, 7.10, 8.04.
5. Compile EMAN on OS X to use on your own machine. *new*
6. Compile EMAN on OS X and package for distribution. *new*
Environement Variable Setting For EMAN
We need set up environment variables like PATH, LD_LIBRARY_PATH and PYTHONPATH for EMAN to working correctly.
These environment variables will be automatically set when you run eman-installer script when you install binary EMAN release.
But for people compile from source and other diagnosis purpose, user may want to know how those environment variables should be set.
- For sh/bash like shells on Linux/UNIX system (suppose you install EMAN under your home directory):
export EMANDIR=${HOME}/EMAN
export PATH=${PATH}:${EMANDIR}/bin
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${EMANDIR}/lib
export PYTHONPATH=${PYTHON_PATH}:${EMANDIR}/lib
- For csh/tcsh like shell on Linux/UNIX system (suppose you install EMAN under your home directory):
setenv EMANDIR ${HOME}/EMAN
setenv PATH ${PATH}:${EMANDIR}/bin
setenv LD_LIBRARY_PATH ${EMANDIR}/lib
setenv PYTHONPATH ${EMANDIR}/lib - For windows system (suppose you install EMAN under C:\):
right click "my computer"->properties->Advanced->Environment Variables, edit the "path" entry, -> then add the EMAN's bin and lib directory into it. Add PYTHONPATH to EMAN's lib directory.