From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: Re: Putting .h files into lib_SOURCES?
Date: Sun, 8 May 2011 01:55:19 +0200 [thread overview]
Message-ID: <201105080155.21020.bruno@clisp.org> (raw)
In-Reply-To: <4DC5BABE.3070304@cs.ucla.edu>
Paul Eggert wrote:
> I'll CC: this to bug-gnulib, as it raises the more-general issue
> of why we ever put gnulib's .h files into lib_SOURCES.
Ralf Wildenhues answered this question on 2011-01-12 [1]:
"things like 'make tags ctags cscope' etc. look at all _SOURCES files."
I never use these targets 'tags', 'ctags', 'cscope', so for me personally
it makes no difference whether .h files are added to lib_SOURCES or not.
But if we decide that .h files should be added to lib_SOURCES, I would vote
for gnulib-tool to do this automatically (like it automatically adds all
source files that are not otherwise mentioned to EXTRA_DIST).
Bruno
[1] http://lists.gnu.org/archive/html/bug-gnulib/2011-01/msg00201.html
--
In memoriam The victims of the Skelani massacre <http://books.google.de/books?id=nltdtAo38K0C&pg=PA41&lpg=PA41&source=bl&ots=DX2VTN1nga&sig=d_BXUZM0I81hZtfrSBA3392p-KY&hl=de&ei=JHy6TcGTCYmLswbpsrDzBQ&sa=X&oi=book_result&ct=result&resnum=1&ved=0CBkQ6AEwAA#v=onepage&q&f=false>
prev parent reply other threads:[~2011-05-07 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 9:35 Changes in lib/ Eli Zaretskii
2011-05-07 21:33 ` Putting .h files into lib_SOURCES? (was: Changes in lib/) Paul Eggert
2011-05-07 23:55 ` Bruno Haible [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201105080155.21020.bruno@clisp.org \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).