On 09/16/2011 03:30 PM, Eric Blake wrote:
On 09/16/2011 03:28 PM, Reuben Thomas wrote:
On 16 September 2011 22:27, Eric Blake<ebl...@redhat.com> wrote:
I'd keep this as:
@item
Use @code{AC_DEFINE} but have @command{configure} compute the literal
value of @code{datadir} and others.
This solution does not conform to the GNU Coding Standards.
that is, just remove the mention of the obsolete archive macro.
Why document a solution that is non-GCS compliant when there are
GCS-compliant solutions?
For teaching purposes. Look at the context - this is part of a larger
list of @items, each giving pros and cons about potential solutions,
before settling on WHY we picked the last bullet as our preferred solution.
But to be honest, we could reorder that list a bit: float the @item on
AC_DEFIN to the front of the list, since it's the worst solution, split
the @item about compile-time substitutions into two (one using -D, and
one using a dedicated header), all before settling on the last @item of
computing runtime relativity to $prefix.
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
