From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unofficial Gentoo Development Guide and Autotools
Date: Fri, 20 May 2005 15:06:12 +0900 [thread overview]
Message-ID: <20050520060612.GA10306@ols-dell.gg3.net> (raw)
In-Reply-To: <20050520060621.6a82957a@snowdrop>
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
maillog: 20/05/2005-06:06:21(+0100): Ciaran McCreesh types
> On Thu, 19 May 2005 04:44:25 +0100 Ciaran McCreesh <ciaranm@gentoo.org>
> wrote:
> | http://www.firedrop.org.uk/devmanual/general-concepts/autotools/
>
> Updated based upon the feedback, thanks guys. If someone who's
> relatively clueless about autotools could give it a read and let me know
> what is and isn't clear I'd appreciate it.
That would be me.
Notes:
- typo?
- The configure script is run to produce one or Makefile files from Makefile.in files.
+ The configure script is run to produce one or more Makefile files from Makefile.in files.
- clarification
AC_MSG_CHECKING(--enable-cscope argument)
AC_ARG_ENABLE(cscope,
[ --enable-cscope Include cscope interface.],
[enable_cscope=$enableval],
[enable_cscope="no"])
AC_MSG_RESULT($enable_cscope)
if test "$enable_cscope" = "yes"; then
AC_DEFINE(FEAT_CSCOPE)
fi
<1 paragraph skipped>
Important: The third argument is used when an option is
specified, and the fourth is used when an option is not
specified. A common misconception is that the third is enable
and the fourth is disable — this is not the case. You may
encounter packages that get this wrong.
The phrase "when an option is specified" is a bit ambiguous, especially
since it is later referred by the explanation of AC_ARG_WITH. I was not
sure if "option" in this case means "option" as in
"--enable-foo=OPTION". I was confused, because one paragarph before the
example you talk about "--enable-foo and --disable-foo *switches* to
./configure".
Maybe the above can be written as: ‟The third argument is used when
either "--enable" or "--disable" is specified, and the fourth is used
when neither is specified.” Or you could simply stick to using
"switches" instead of "options"?
- coloring
%.1 : %.in
@regex_cmd@ -e "s,\@VERSION\@,$(VERSION),g" $? > $@
The first "@" is span.Special and the second one is span.Constant.
Good job by the way.
--
() Georgi Georgiev () There is only one thing in the world worse ()
() chutz@gg3.net () than being talked about, and that is not ()
() +81(90)2877-8845 () being talked about. -- Oscar Wilde ()
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-20 6:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 3:44 [gentoo-dev] Unofficial Gentoo Development Guide and Autotools Ciaran McCreesh
2005-05-19 5:27 ` Donnie Berkholz
2005-05-19 5:43 ` Mike Frysinger
2005-05-19 12:48 ` Mike Frysinger
2005-05-19 5:48 ` Mike Frysinger
2005-05-19 12:06 ` Stephen Bennett
2005-05-19 17:53 ` Chris White
2005-05-19 18:59 ` Mike Frysinger
2005-05-19 19:06 ` Mike Frysinger
2005-05-19 19:47 ` Chris White
2005-05-19 20:14 ` Mike Frysinger
2005-05-20 5:06 ` Ciaran McCreesh
2005-05-20 6:06 ` Georgi Georgiev [this message]
2005-05-20 6:22 ` Ciaran McCreesh
2005-05-20 9:01 ` Georgi Georgiev
2005-05-20 9:29 ` Ciaran McCreesh
2005-05-20 10:11 ` Georgi Georgiev
2005-05-20 22:10 ` Ciaran McCreesh
2005-05-20 9:40 ` Georgi Georgiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050520060612.GA10306@ols-dell.gg3.net \
--to=chutz@gg3.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox