summaryrefslogtreecommitdiffstats
path: root/INSTALL
blob: 805ae36456fd95824e449c35eb6d73f1fe9dfdaf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
To build/install HDF5 on Unix systems from the root of the
distribution directory:

   * Build the ./src/H5config.h file and Makefiles by saying:

	./configure

     You can say `./configure --help' to see a list of options.  On
     common option is to specify the prefix directory where the
     libraries, header files, and programs are installed.  The default
     is to install them in /usr/local/lib, /usr/local/include, and
     /usr/local/bin, but you can specify some other path instead of
     /usr/local by saying:

	./configure --prefix=/usr

     You can also override detection of certain things with
     environment variables:

	CC		Name of the C compiler to use.
	CFLAGS		Alternate C compiler flags.
	CPPFLAGS	Alternate C preprocessor flags.
	MAKE		Name of the make(1) program.

     For instance (assuming /bin/sh), it is common to say:

	CPPFLAGS=-DNDEBUG CC=gcc CFLAGS=-O3 ./configure


   * Build library targets by saying:

	make

     If you ran configure like (assuming /bin/sh):

	MAKE=gmake ./configure

     then you'll want to be sure to use `gmake' also when you build
     the library.  If you're re-building the library after changing
     some files and you're not using GNU make and gcc, then you should
     say `make clean' from the top directory between each build
     attempt.

   * Install the library, header files, and programs by saying:

	make install

     This step will fail unless you have permission to write to the
     installation directories.

To build/install HDF5 on non-Unix systems from the root of the
distribution directory:

   * To be written later.