cheng/libpng
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[libpng16] Updated INSTALL to explain that autogen.sh must be run in a GIT

Browse Source 
clone, not in a directory extracted from a tar distribution.
This commit is contained in:
Glenn Randers-Pehrson 2012-01-31 22:15:30 -06:00
parent 3167541570
commit 34dca8f8e8
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
INSTALL
View File

@ -9,21 +9,26 @@ On Unix/Linux and similar systems, you can simply type
and ignore the rest of this document. and ignore the rest of this document.
If configure does not work on your system and you have a reasonably If configure does not work on your system, or if you have a need to
up-to-date set of tools, running ./autogen.sh before running ./configure change configure.ac or Makefile.am, and you have a reasonably
may fix the problem. You can also run the individual commands in up-to-date set of tools, running ./autogen.sh in a git clone before
autogen.sh with the --force option, if supported by your version of running ./configure may fix the problem. To be really sure that you
the tools. To be really sure that you aren't using any of the included aren't using any of the included pre-built scripts, you can do this:
pre-built scripts, you can do this:
./configure --enable-maintainer-mode ./configure --enable-maintainer-mode
make maintainer-clean make maintainer-clean
./autogen.sh ./autogen.sh # only in a GIT clone; see below!
./configure [--prefix=/path] [other options] ./configure [--prefix=/path] [other options]
make make
make install make install
make check make check
As of libpng-1.6.0, autogen.sh only works properly in a
git clone. If you are working with a tar distribution, you must
get a git clone, run autogen.sh there, and then copy the resulting
configuration files from there to your working directory. Then you can
run configure and make as previously with earlier versions of libpng.
Instead, you can use one of the custom-built makefiles in the Instead, you can use one of the custom-built makefiles in the
"scripts" directory "scripts" directory