INSTALL 5.2 KB
Newer Older
1

2
Installing libpng version 1.4.0beta107 - November 27, 2009
3

4 5
On Unix/Linux and similar systems, you can simply type

6
    ./configure [--prefix=/path]
7 8 9 10 11
    make check
    make install

and ignore the rest of this document.

12 13 14 15 16 17 18 19 20 21
If configure does not work on your system and you have a reasonably
up-to-date set of tools, running ./autogen.sh before running ./configure
may fix the problem.  You can also run the individual commands in
autogen.sh with the --force option, if supported by your version of
the tools.  If you run 'libtoolize --force', though, this will replace
the distributed, patched, version of ltmain.sh with an unpatched version
and your shared library builds may fail to produce libraries with the
correct version numbers.

Instead, you can use one of the custom-built makefiles in the
22 23 24 25 26 27
"scripts" directory

    cp scripts/makefile.system makefile
    make test
    make install

28 29 30
The files that are presently available in the scripts directory
are listed and described in scripts/README.txt.

31 32 33 34 35 36 37
Or you can use one of the "projects" in the "projects" directory.

Before installing libpng, you must first install zlib, if it
is not already on your system.  zlib can usually be found
wherever you got libpng.  zlib can be placed in another directory,
at the same level as libpng.

G
Glenn Randers-Pehrson 已提交
38
If you want to use "cmake" (see www.cmake.org), type
39 40 41 42 43

   cmake . -DCMAKE_INSTALL_PREFIX=/path
   make
   make install

44 45 46
If your system already has a preinstalled zlib you will still need
to have access to the zlib.h and zconf.h include files that
correspond to the version of zlib that's installed.
47 48

You can rename the directories that you downloaded (they
49
might be called "libpng-1.4.0beta107" or "libpng14" and "zlib-1.2.3"
50
or "zlib123") so that you have directories called "zlib" and "libpng".
51 52 53 54 55 56 57 58 59

Your directory structure should look like this:

   ..       (the parent directory)
      libpng  (this directory)
          INSTALL (this file)
          README
          *.h
          *.c
60
          CMakeLists.txt    =>  "cmake" script
61 62
          configuration files:
             configure.ac, configure, Makefile.am, Makefile.in,
63 64 65 66
%12-%             autogen.sh, config.guess, ltmain.sh, missing,
%12-%             aclocal.m4, config.h.in, config.sub,
%14+%             autogen.sh, config.guess, ltmain.sh, missing, libpng-pc.in,
%14+%             libpng-config.in, aclocal.m4, config.h.in, config.sub,
67
             depcomp, install-sh, mkinstalldirs, test-pngtest.sh
68 69
          contrib
             gregbook
70
             pngminim
71 72
             pngminus
             pngsuite
73
             visupng
74
          projects
75
             cbuilder5 (Borland)
76
             visualc6 (msvc)
77 78
             visualc71
             xcode
79 80
          scripts
             makefile.*
81
             *.def (module definition files)
82 83 84 85 86 87 88 89 90
          pngtest.png
          etc.
      zlib
          README
          *.h
          *.c
          contrib
          etc.

91 92 93 94
If the line endings in the files look funny, you may wish to get the other
distribution of libpng.  It is available in both tar.gz (UNIX style line
endings) and zip (DOS style line endings) formats.

95
If you are building libpng with MSVC, you can enter the
96 97
libpng projects\visualc6 or visualc71 directory and follow the instructions
in README.txt.
98

99
Otherwise enter the zlib directory and follow the instructions in zlib/README,
100 101
then come back here and run "configure" or choose the appropriate
makefile.sys in the scripts directory.
102

103 104 105
Copy the file (or files) that you need from the
scripts directory into this directory, for example

106
   MSDOS example: copy scripts\makefile.msc makefile
107 108 109 110 111 112 113 114
   UNIX example:    cp scripts/makefile.std makefile

Read the makefile to see if you need to change any source or
target directories to match your preferences.

Then read pngconf.h to see if you want to make any configuration
changes.

115 116 117 118 119 120 121
Then just run "make" which will create the libpng library in
this directory and "make test" which will run a quick test that reads
the "pngtest.png" file and writes a "pngout.png" file that should be
identical to it.  Look for "9782 zero samples" in the output of the
test.  For more confidence, you can run another test by typing
"pngtest pngnow.png" and looking for "289 zero samples" in the output.
Also, you can run "pngtest -m contrib/pngsuite/*.png" and compare
122
your output with the result shown in contrib/pngsuite/README.
123 124 125 126

Most of the makefiles will allow you to run "make install" to
put the library in its final resting place (if you want to
do that, run "make install" in the zlib directory first if necessary).
127
Some also allow you to run "make test-installed" after you have
128
run "make install".
129

130 131
If you encounter a compiler error message complaining about the
lines
132

133 134
      __png.h__ already includes setjmp.h;
      __dont__ include it again.;
135 136

this means you have compiled another module that includes setjmp.h,
137 138 139 140 141 142
which is hazardous because the two modules might not include exactly
the same setjmp.h.  If you are sure that you know what you are doing
and that they are exactly the same, then you can comment out or
delete the two lines.  Better yet, use the cexcept interface
instead, as demonstrated in contrib/visupng of the libpng distribution.

143
Further information can be found in the README and libpng.txt
144 145
files, in the individual makefiles, in png.h, and the manual pages
libpng.3 and png.5.