|
From: | Eric Blake |
Subject: | Re: Make AX_DEFINE_DIR obsolete? |
Date: | Fri, 16 Sep 2011 15:36:33 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110831 Fedora/3.1.12-2.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.12 |
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<address@hidden> 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 address@hidden +1-801-349-2682 Libvirt virtualization library http://libvirt.org
[Prev in Thread] | Current Thread | [Next in Thread] |