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