| 59 | | sudo ln -s $HOME/src/Chimera64-daily/bin/chimera /usr/local/bin/chimera |
| 60 | | }}} |
| 61 | | |
| 62 | | Lastly, a few environment variables are set to simplify executing the new installation programs. If your installation path is different, you will need to set the CHIMERA environment variable to your path. |
| 63 | | {{{ |
| 64 | | export CHIMERA=$HOME/src/Chimera64-daily |
| | 59 | sudo ln -s $HOME/src/Chimera64-daily/bin/chimera /usr/local/bin/chimera-daily |
| | 60 | }}} |
| | 61 | |
| | 62 | If I run a build from svn-source, I create symlink for that too, something like: |
| | 63 | In addition, I like to setup a few symlinks, like so: |
| | 64 | {{{ |
| | 65 | cd ~/src |
| | 66 | ln -s Chimera64-build31263 Chimera64-build |
| | 67 | sudo ln -s $HOME/src/Chimera64-build/bin/chimera /usr/local/bin/chimera-build |
| | 68 | }}} |
| | 69 | |
| | 70 | Lastly, a few environment variables are set to simplify executing the new installation programs. If your installation path is different, you will need to set the CHIMERA environment variable to your path. The CHIMERA path must point to a hard-link, not a sym-link, in the directory tree. |
| | 71 | {{{ |
| | 72 | # For a daily build, use: |
| | 73 | export CHIMERA=$(cd $HOME/src/Chimera64-daily && pwd -P) |
| | 74 | # For an svn-build, use: |
| | 75 | #export CHIMERA=$(cd $HOME/src/Chimera64-build && pwd -P) |