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