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 with slightly
9 longer descriptions in README.configure
11 You might look at the "defaultconfig" file in the top directory.
12 It is an example of what is probably reasonable for defaults.
14 Some systems require unusual options for compilation or linking that
15 the `configure' script does not know about. You can give `configure'
16 initial values for variables by setting them in the environment. Using
17 a Bourne-compatible shell, you can do that on the command line like
19 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
20 Or on systems that have the `env' program, you can do it like this:
21 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
22 Or if you're using a non Bourne-compatible shell, you can do:
23 sh -c 'CFLAGS="-O2 -g" ./configure
25 A typical Bacula development configuration for Linux is:
27 CFLAGS="-g -Wall" ./configure --enable-smartalloc --enable-mysql
29 see README for a few additional details and the online manual
30 for all the gory details: http://www.bacula.org/html-manual
33 3. set any other main preferences (normally, you don't do this):
34 Edit "config.h" if you didn't use ./configure options
35 If you're cross-compiling, edit the following in "config.h"
37 4. Build it (repeat step 2 as desired):