There are a couple of PATH variables you may want to set.
The LD_LIBRARY_PATH should be set like this:
What that does is place the path to ".../dist/lib" before your existing LD_LIBRARY_PATH (if any). If you were to add an additional LD_LIBRARY_PATH variable to this, you would do it like this:
That adds the new path to the previous path. The colon (
Bear in mind that LD_LIBRARY_PATH is "where to look for libraries;" e.g., files named something like libabc.a
. It is highly unlikely that an include
directory will have library files in it (include files are usually file.h
and are used by the compiler) -- best check that.
Execution path, the PATH environment variable, is set similarly:
You can set these in an individual user's .profile
file or you can set them system-wide. If you set them in a user's .profile
they'll be available to that user (say, a user that will be using the software you've added). If you set them system-wide, that can be done in /etc/profile
(so every user will have the paths) or, better, if you have a directory /etc/profile.d
, you can add a small executable shell program ("script") there. For example, this file sets up the path environment for a application named GMT on my systems:
# Name: $Source$
# Version: $Revision$
# Modified: $Date$
# Purpose: set local environment variables for GTM and netCDF
# Author: T. N. Ronayne
# Date: 1 Oct 2009
# Set the local system $PATH:
The file, /etc/profile.d/gmt.sh
is executable; i.e., it was created with a text editor then
chmod 755 /etc/profile.d/gmt.sh
NOTE: if you do not have an existing /etc/profile.d
directory, do not do the above, simply add the lines in user .profile
files or append them to the end of /etc/profile
or refer to your documentation for how to do this in Fedora; the method is the same but where to put it may not be.
Hope this helps some.