autoconf
[Top][All Lists]
Advanced

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

[Autoconf] Re: HTML format documentation


From: Richard Stallman
Subject: [Autoconf] Re: HTML format documentation
Date: Fri, 15 Sep 2000 16:29:04 -0600 (MDT)

The GNU coding standards explicitly specifies the possible configure
options.  Whatever names we choose for new options, they will have to
be given in the coding standards.  They will not be exceptions, they
will be defined options.

    I agree, and this is why I proposed to move the foodir into the domain
    of variables too.  But certainly not --with and --enable etc. because
    these are truly options.

I do not see the difference that you refer to.  Would you please
propose to me a criterion for deciding what should be a variable and
what should be an option?

    But in the case of CC, CFLAGS etc. these guys are traditional envvars,
    they have deeply a nature of variables.

Sorry, I don't see this "nature" at all.  I only see that you're
proposing two different ways of specify data for configure,
and I don't know how I would figure out which of the two ways
is used for any given datum.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]