From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Why <config.h> and not "config.h" ?
Date: Wed, 28 Jul 2010 09:46:42 +0200 [thread overview]
Message-ID: <87y6cwqc9p.fsf@telefonica.net> (raw)
In-Reply-To: 87d3u8cc0s.GNU's_Not_Unix!%yavor@gnu.org
Yavor Doganov <yavor@gnu.org> writes:
>> Emacs sources use the idiom
>>
>> #include <config.h>
>
> The Autoconf manual recommends this practice.
Yes, for the very same reason Miles explained. Quoting from the manual:
"With the appropriate -I option, you can use ‘#include
<config.h>’. Actually, it's a good habit to use it, because in the rare
case when the source directory contains another config.h, the build
directory should be searched first."
I'll emphasize the phrase "With the appropriate -I option." Otherwise
having a config.h on the source directory in a out of tree build is
asking for trouble.
next prev parent reply other threads:[~2010-07-28 7:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 2:23 Why <config.h> and not "config.h" ? Óscar Fuentes
2010-07-28 2:30 ` Miles Bader
2010-07-28 3:25 ` Óscar Fuentes
2010-07-28 6:30 ` Jan Djärv
2010-07-28 6:46 ` Óscar Fuentes
2010-07-28 7:06 ` Jan Djärv
2010-07-28 7:35 ` Óscar Fuentes
2010-07-28 7:57 ` Jan Djärv
2010-07-28 8:04 ` immanuel litzroth
2010-07-28 8:19 ` Jan Djärv
2010-07-28 9:38 ` Óscar Fuentes
2010-07-28 10:07 ` Óscar Fuentes
2010-07-28 8:29 ` Andreas Schwab
2010-07-28 8:59 ` Óscar Fuentes
2010-07-29 14:26 ` Stefan Monnier
2010-07-30 9:21 ` Stephen J. Turnbull
2010-07-30 9:55 ` Eli Zaretskii
2010-08-01 9:31 ` Stephen J. Turnbull
2010-07-28 7:06 ` Andreas Röhler
2010-07-28 7:10 ` Óscar Fuentes
2010-07-28 7:15 ` Yavor Doganov
2010-07-28 7:46 ` Óscar Fuentes [this message]
2010-07-28 19:50 ` Dan Nicolaescu
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=87y6cwqc9p.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.