[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using $bindir in configure.ac
From: |
Stepan Kasal |
Subject: |
Re: Using $bindir in configure.ac |
Date: |
Fri, 7 Jan 2005 10:52:49 +0100 |
User-agent: |
Mutt/1.4.1i |
Hello,
On Thu, Jan 06, 2005 at 02:30:34PM +0100, Magnus Therning wrote:
> AC_PROGRAM([MY_PROGR], [mypr], [no], [$bindir:$PATH])
>
> but it doesn't seem to work. $bindir is expanded to ${exec_prefix}/bin,
> on top of that it seems $exec_prefix still is NONE (i.e. a double
> expansion, if I could even trigger it, wouldn't suffice) since I only
> use --prefix on the command line. Any suggestions?
I believe the double expansion is the way to go.
I invented the following:
bindir_path=`eval "case $prefix$exec_prefix in \
NONENONE) exec_prefix=$ac_default_prefix;; \
*NONE) exec_prefix=$prefix;;esac; echo $bindir"`
AC_PROGRAM([MY_PROGR], [mypr], [no], [$bindir_path:$PATH])
Of course, many other solutions are possible, you can use sed, for example.
HTH,
Stepan Kasal
- Using $bindir in configure.ac, Magnus Therning, 2005/01/06
- Re: Using $bindir in configure.ac, Magnus Therning, 2005/01/07
- Re: Using $bindir in configure.ac, Bob Friesenhahn, 2005/01/07
- Re: Using $bindir in configure.ac, Magnus Therning, 2005/01/08
- Re: Using $bindir in configure.ac, Stepan Kasal, 2005/01/10
- Re: Using $bindir in configure.ac, Stepan Kasal, 2005/01/10
- Re: Using $bindir in configure.ac, Andreas Schwab, 2005/01/10
- Re: Using $bindir in configure.ac, Stepan Kasal, 2005/01/10
- Re: Using $bindir in configure.ac, Andreas Schwab, 2005/01/10
- Re: Using $bindir in configure.ac, Stepan Kasal, 2005/01/11
- Re: Using $bindir in configure.ac, Peter Simons, 2005/01/15