Re: configure options for directory variables in standards.texi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



    Using $(FOO) [or ${FOO} - same] allows the user to override FOO when
    invoking make.

Sure.  My question was about recommending $(...) for Automake users
instead of ${...}.  Let's take an example.  Here's one of the
descriptions as it is written now:

    `bindir'
         The directory for installing executable programs that users can
         run.  This should normally be `/usr/local/bin', but write it as
         `$(exec_prefix)/bin'.  (If you are using Autoconf, write it as
         `@bindir@'.)

Here's my understanding of what Ralf is proposing:

    `bindir'
         The directory for installing executable programs that users can
         run.  This should normally be `/usr/local/bin', but write it as
         `${exec_prefix}/bin'.  (If you are using Autoconf, write it as
         `@bindir@'; if you are using Automake and need to refer to it,
         write it as `$(bindir)'.)

My question was, can you refer to it as ${bindir} in Automake, so we are
recommending the same syntax for the automake and no-autotools cases?
(This is not a question about make or shells or perl or anything else. :)

Thanks,
karl


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux