different versions of the same binary package.
A relocatable program can be moved or copied to a different location
-on the filesystem. It is possible to make symlinks to the installed
+on the file system. It is possible to make symlinks to the installed
and moved programs, and invoke them through the symlink. It is
possible to do the same thing with a hard link @emph{only} if the hard
link file is in the same directory as the real program.
This approach does not always work. On OpenBSD and OpenServer,
prereleases of Libtool 1.5 put absolute file names of libraries in
-executables, which prevents searching any other locations.
+executables, which prevents searching any other locations.
@item
On Windows, the executable's own directory is searched for libraries,
@noindent
becomes:
-@example
+@example
bindtextdomain (PACKAGE, relocate (LOCALEDIR));
@end example
@end example
@item
-You may also need to add one or two variable assignments to your
-@file{configure.ac}.
+You may also need to add a couple of variable assignments to your
+@file{configure.ac}.
If your package (or any package you rely on, e.g.@: gettext-runtime)
will be relocated together with a set of installed shared libraries,
RELOCATABLE_CONFIG_H_DIR='$(top_builddir)/src'
@end example
@end enumerate
+
+Set @var{RELOCATABLE_STRIP} to @code{:}. This is needed so that
+@samp{make install} installs executables without stripping them.