Mail Archives: djgpp/1999/07/04/08:50:18
On Thu, 1 Jul 1999, Mark E. wrote:
> One idea I have for a new update that I'd like comments on would be to
> include a config.site as described in the Autoconf docs.
I think this is a good idea. I attach below the version of
config.site that I usually put inside ported packages, to be used
during the configure step.
> That script could
> set PATH_SEPARATOR to ':' (just in case someone changes the default), then
> do stuff like this:
>
> if test -x ${DJDIR}/gcc.exe; then
> export CC=${DJDIR}/gcc.exe
> fi
>
> if test -x ${DJDIR}/gpp.exe; then
> export CXX=${DJDIR}/gpp.exe
> fi
If PATH_SEPARATOR is set to :, then you shouldn't need to set CC and
CXX because the configure script will find the compiler automatically,
provided that test -f is solved like I explain below.
> to get around the 'test -f' problem and allow configure scripts to work
> without regenerating then.
The idea is not to generate test -x *instead* of test -f, but rather
make the configure script use one or the other, depending whether it
runs on Unix or on DOS/Windows.
--------------------- suggested config.site --------------------
#! /bin/sh
# This is the config.site file for configuring GNU packages
# which are to be built with DJGPP tools.
# These two variables are required, otherwise looking for
# programs along the PATH will not work.
PATH_SEPARATOR=:
PATH_EXPAND=y
# The root of the DJGPP tree serves as the default prefix
test "x$prefix" = xNONE && prefix='${DJDIR}'
# This is required for config.status script to be run, since
# ./configure runs it by invoking ${CONFIG_SHELL-/bin/sh}
CONFIG_SHELL=${CONFIG_SHELL='sh'}
# These are set here so the generated Makefile's will be good
# for every DJGPP installation, not only the one where the
# package was configured.
# $INSTALL must be an absolute path name, otherwise config.status
# will try to prepend ./ and ../ to it when it goes into subdirs.
INSTALL=${INSTALL='${DJDIR}/bin/ginstall -c'}
RANLIB=${RANLIB='ranlib'}
- Raw text -