[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: including autoconf paths in source
From: |
Monty Taylor |
Subject: |
Re: including autoconf paths in source |
Date: |
Sat, 20 Dec 2008 20:50:53 -0800 |
User-agent: |
Thunderbird 2.0.0.18 (X11/20081125) |
Eric Blake wrote:
> According to Monty Taylor on 12/20/2008 11:57 AM:
>> I'm wondering if it would be worthwhile to add an AC_DEFINE form, like
>> AC_DEFINE_EXPANDED, that would fully-expand things before putting them
>> in config.h.
>
> No, because that would violate GNU Coding Standards that the user be able
> to override $(prefix) at make time and have it affect all the other
> variables. Really, the best solution is to do exactly what we have
> already pointed you to - the gnulib module configmake is the ideal example
> of how to propagate these variables into source code:
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=modules/configmake;h=5160128;hb=78f5fbf
>
AH, ok. Well, the configmake solution is working well... and that makes
perfect sense as to why there is not an AC_DEFINE_EXPANDED.
Thanks!
Monty
- Re: including autoconf paths in source, (continued)
- Re: including autoconf paths in source, Thomas Dickey, 2008/12/12
- Re: including autoconf paths in source, Ralf Corsepius, 2008/12/12
- Re: including autoconf paths in source, Thomas Dickey, 2008/12/12
- Re: including autoconf paths in source, Ralf Corsepius, 2008/12/12
- Re: including autoconf paths in source, Thomas Dickey, 2008/12/12
- Re: including autoconf paths in source, John Calcote, 2008/12/12
- Re: including autoconf paths in source, Ralf Corsepius, 2008/12/12
- Re: including autoconf paths in source, Monty Taylor, 2008/12/20
- Re: including autoconf paths in source, Jan Engelhardt, 2008/12/20
- Re: including autoconf paths in source, Eric Blake, 2008/12/20
- Re: including autoconf paths in source,
Monty Taylor <=