| 36 | | __'''NOTE'''__: As you know, in order to compile and run PALM, the PATH and PALM_BIN variables need to be set in your shell environment (e.g. .profile or .bashrc) as in this example: |
| | 36 | __'''NOTE'''__: As you know, in order to compile and run PALM, the {{{PATH}}} and {{{PALM_BIN}}} variables need to be set in your shell environment (e.g. {{{.profile}}} or {{{.bashrc}}}) as in this example: |
| | 37 | |||| {{{ #PALM SCRIPTS}}} \\ {{{export PATH=$HOME/palm/current_version/trunk/SCRIPTS:$PATH }}}\\ {{{export PALM_BIN=$HOME/palm/current_version/trunk/SCRIPTS }}} || |
| | 38 | |
| | 39 | These __paths need to be adjusted__ when you run PALM out of your {{{~/palm/branches/<feature_name>}}} directory! \\ You might have to newly login to your system in order to activate these changes. You can check the paths by typing {{{echo $PATH}}} or {{{echo $PALM_BIN}}} to your terminal. |
| | 40 | |
| | 41 | An alternative to this approach is to __use symbolic links__ to link {{{.../trunk to .../branches/<feature_name>}}}. \\ This way you don't have to keep changing the {{{PATH/PALM_BIN}}} variables, and you run PALM out of your current_version directory, with your {{{SCRIPTS/SOURCE}}} files from {{{~/palm/branches/<feature_name>}}} |
