2 This file is rather out of date, and if you want to avoid a lot
3 of pain, you will read the manual, which you can find at www.bacula.org
6 --------------------------------------------------------------------------
8 --------------------------------------------------------------------------
9 1. Read the Compiling and Installing section of the HTML manual
10 at http://www.bacula.org
12 2. Run ./configure to generate config.h and the various Makefiles.
13 ./configure --help gives a list of possible options. Note, in
14 configuring Bacula, you cannot get by with a simple ./configure,
15 it is much more complicated than that (unfortunately).
17 You might look at the "defaultconfig" file in the examples directory.
18 It is an example of what is probably reasonable for defaults.
20 Some systems require unusual options for compilation or linking that
21 the `configure' script does not know about. You can give `configure'
22 initial values for variables by setting them in the environment. Using
23 a Bourne-compatible shell, you can do that on the command line like
25 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
26 Or on systems that have the `env' program, you can do it like this:
27 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
28 Or if you're using a non Bourne-compatible shell, you can do:
29 sh -c 'CFLAGS="-O2 -g" ./configure
31 A typical Bacula development configuration for Linux is:
33 CFLAGS="-g -O2 -Wall" \
35 --sbindir=$HOME/bacula/bin \
36 --sysconfdir=$HOME/bacula/bin \
37 --with-pid-dir=$HOME/bacula/bin/working \
38 --with-subsys-dir=$HOME/bacula/bin/working \
41 --with-working-dir=$HOME/bacula/bin/working \
42 --with-dump-email=your@address.com \
43 --with-job-email=your@address.com \
44 --with-smtp-host=localhost
47 See the README for a few additional details and the online manual
48 for all the gory details: http://www.bacula.org/rel-manual
50 3. Carefully review the output from ./configure. If it is not
51 what you want, re-run the ./configure. Often ./configure "caches"
52 things and thus remembers the last ./configure options. If you
53 want to be sure you are starting fresh after a ./configure,
58 before re-running ./configure. "make distclean" wipes out any
59 knowledge of the ./configure, so don't do it after you have a
60 configuration that suits your needs, otherwise the "make" will
63 4. Set any other main preferences (normally, you don't do this):
64 Edit "config.h" if you didn't use ./configure options
65 If you're cross-compiling, edit the following in "config.h"
67 5. Build it (repeat step 2 as desired):