2005-04-25 20:36:43 +04:00
|
|
|
#! /bin/sh
|
|
|
|
# This script makes the autoconf mechanism for the Unix port work.
|
|
|
|
# It's separate from mkfiles.pl because it won't work (and isn't needed)
|
|
|
|
# on a non-Unix system.
|
|
|
|
|
2008-04-02 21:09:53 +04:00
|
|
|
# It's nice to be able to run this from inside the unix subdir as
|
|
|
|
# well as from outside.
|
|
|
|
test -f unix.h && cd ..
|
|
|
|
|
Switch to using automake for the Unix autoconfigured build.
mkfiles.pl no longer generates a Makefile.in, but instead generates a
Makefile.am on which mkauto.sh runs automake. This means that the
autoconfigured makefile now does build-time dependency tracking (a
standard feature of automake-generated makefiles), and is generally
more like what Unix people will expect.
Some of the old-style make command-line settings (VER=-DRELEASE=foo,
XFLAGS=-DDEBUG) will still work; the COMPAT settings are better done
by autoconfiguration, and my habitual 'XFLAGS="-g -O0"' for an easily
debuggable build will actually not work any more because CFLAGS is
specified _after_ XFLAGS, so I should instead write 'make CFLAGS=-O0'
(-g is the default in automake, removed at 'make install' time).
The new makefile will automatically degrade into one that builds the
command-line tools only, in the case where GTK could not be found. In
principle, therefore, it should be an adequate replacement for _both_
the static Unix makefiles, Makefile.gtk and Makefile.ux. I haven't
actually retired those in this commit, but I'm pretty tempted.
[originally from svn r9239]
2011-07-23 15:33:29 +04:00
|
|
|
# Run autoconf on our real configure.in.
|
|
|
|
(cd unix && autoreconf -i && rm -rf autom4te.cache)
|