to explicitly specify the libraries directory on the ./configure
line (--libdir=/full-path/dir), but this should not be necessary.
+ ./configure --libdir=<full-path>
+
If you have problems with libtool or you wish to use the old
way of building libraries and linking them into Bacula, you
can do so by disabling libtool on the configure command line with:
want to put them elsewhere use:
./configure --docdir=<full-path>
+
+During the installation of Bacula, any plugins will be
+installed in the plugindir, which is by default the
+same as libdir (/usr/lib). You can specify an alternate
+location with:
+
+ ./configure --with-plugindir=<full-path>
+
==============================================================
This release includes large number of new features and changes.
# ------------------------------------------
# Where to place plugindir (plugin files)
# ------------------------------------------
-plugindir=`eval echo ${sysconfdir}`
+plugindir=`eval echo ${libdir}`
AC_ARG_WITH(plugindir,
AC_HELP_STRING([--with-plugindir=PATH], [specify path of Bacula plugins directory]),
[
# ------------------------------------------
# Where to place plugindir (plugin files)
# ------------------------------------------
-plugindir=`eval echo ${sysconfdir}`
+plugindir=`eval echo ${libdir}`
# Check whether --with-plugindir was given.
if test "${with_plugindir+set}" = set; then
General:
+06Apr09
+kes Change default plugins dir to /usr/lib.
05Apr09
kes Fix Win32 make clean to clean correctly
kes Cleanup Win installer dialog messages a bit ...