all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31744@debbugs.gnu.org
Subject: bug#31744: 26.1; Improvements to make tags and make -C test
Date: Fri, 08 Jun 2018 21:12:04 -0400	[thread overview]
Message-ID: <87po10226z.fsf@gmail.com> (raw)
In-Reply-To: <87po11jmdq.fsf@gmail.com> (Robert Pluim's message of "Fri, 08 Jun 2018 18:04:01 +0200")

>>> * src/Makefile.in: Create TAGS files in ${srcdir}, not build dir.
>>
>> I'm not sure I agree with this.  Other projects I looked at produce
>> TAGS in the build directory (but reference source files in srcdir, of
>> course).  Why do you think TAGS should go to the source directory?

Oh, hmm.  The original reason, is that when looking at a source file in
Emacs, and then hitting M-. I get a prompt to visit the TAGS table,
which starts from the source directory.  Then I have to go looking for
the TAGS file in the corresponding build directory.  This seems kind of
silly, especially since every build directory will have identical TAGS
files anyway (meaning I either have to make TAGS redundantly per-build
directory, or remember exactly which build directory has the TAGS file).

I saw the FIXME in Makefile.in, so I assumed (oops!) this was some
well-known problem, and that nobody had bothered to make the obvious fix
yet.

> They should not. Source should be able to be mounted read-only, and
> all build products should be stored elsewhere.

Emacs puts .elc files in the source directory.  I was under the
impression that the general principal is that arch & config dependent
files go in the build directory, and arch & config independent ones go
in the source directory.






  reply	other threads:[~2018-06-09  1:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  1:49 bug#31744: 26.1; Improvements to make tags and make -C test Noam Postavsky
2018-06-08 15:38 ` Eli Zaretskii
2018-06-08 16:04   ` Robert Pluim
2018-06-09  1:12     ` Noam Postavsky [this message]
2018-06-09  6:20       ` Eli Zaretskii
2018-06-09 19:16         ` Noam Postavsky
2018-06-10 16:59           ` Eli Zaretskii
2018-06-12 11:49             ` Noam Postavsky

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=87po10226z.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31744@debbugs.gnu.org \
    --cc=eliz@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.