diff options
author | David Thompson <dthompson@vistahigherlearning.com> | 2015-10-01 09:25:02 -0400 |
---|---|---|
committer | David Thompson <dthompson@vistahigherlearning.com> | 2015-10-01 09:25:02 -0400 |
commit | f363308fd76135b36b8db0f21b315978e9b846a9 (patch) | |
tree | 7bfd741631a15ae31448d318ec4adb4c0d79177b | |
parent | 7a29c3fc744aac77fb8d39aff47c90ac95ab1fa6 (diff) |
README: Add a note about Guile's load paths.
When installing to a prefix that is different than where Guile itself
was installed, users need to do some extra work to setup their load
paths.
Thanks to ArneBab for the original patch this text was adapted from.
-rw-r--r-- | README | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -44,3 +44,18 @@ arbitrary set of key/value data pairs. #+BEGIN_SRC sh ./bootstrap && ./configure && make && make install #+END_SRC + + Depending on your chosen installation prefix via the =--prefix= + option to the configure script (which defaults to =/usr/local=, + users may need to setup the =GUILE_LOAD_PATH= and + =GUILE_LOAD_COMPILED_PATH= environment variables to include the + directory where Shroud's Guile modules were installed. + + For example, GNU Bash users may add the following snippet to their + =$HOME/.bash_profile=: + + #+BEGIN_SRC sh + export GUILE_LOAD_PATH=/usr/local/share/guile/2.0 + export GUILE_LOAD_COMPILED_PATH=/usr/local/share/guile/2.0 + export PATH=/usr/local/bin:$PATH + #+END_SRC |