This is just a quick note on "local" installs with Player, Stage and
Gazebo. Some developers (myself included) prefer to install these
applications in our user directory (e.g., /home/[username]/local) rather
than in a system directory; this avoids screwing up other users of the
machine if you have some funky experimental code you want to work with.
It's also useful if you dont have root access.
Naturally, local installs can make it a bit tricky for the various
packages to find the right headers, libs and so on. Historically, we have
worked around this by specifying '--with-foo=path' arguments to the
configure scripts; unfortunately, this method is fraught with danger and
is now being phased out. Here, then, is the recommended way to do it:
1) Pick a spot for "local" installs; for me it is "/home/ahoward/local".
The install scripts will create relevant subdirs under this, such as:
2a) Set up the necessary compiler paths in your .bashrc (or whatever)
The first line sets the executable path; the second sets the path for C
and C++ header files; the third line sets the library search path.
2b) Set up some additional paths in your .bashrc (or whatever)
The first line sets the pkg-config path (for applications using
pkg-config, which will be everything in the P/S/G project pretty soon);
the second line is for Python modules (e.g. Python bindings to the
libplayerc client lib).
3) Build applications using the "--prefix" argument; e.g.;
Note that you dont need to be root to do this.
Everything should now build seamlessly without any additional frigging
around, and your locally installed packages will be used in preference to
any system-wide installs.
Andrew Howard email: ahoward@...
Department of Computer Science http: www-robotics.usc.edu/~ahoward
University of Southern California phone: 1 (213) 740 6416
Los Angeles, CA, U.S.A. 90089-0781 fax: 1 (213) 821 5696
<< Insert pithy saying here >>>