From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Building Emacs
Date: Tue, 24 Jun 2008 21:37:57 -0400 [thread overview]
Message-ID: <jwvabhamh9t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <18529.26609.567179.380849@kahikatea.snap.net.nz> (Nick Roberts's message of "Wed, 25 Jun 2008 09:32:33 +1200")
> Maybe it has something to do with using a separate build directory
> (~/emacs/build/) to the source (~/emacs/src)
It could very well be: I never used a separate build directory, so
I don't know what goes where and what can be assumed to be where, so
whenever I touch the Makefiles, I tend to introduce problems in
this area.
The fact that the Makefiles seem to contain somewhere around 0 bytes of
comments about this doesn't help, of course.
>> >> and it insists on generating autoloads for all files in the
>> >> lisp directory.
>> > That was also the case in the past, except that your recipe simply never
>> > updated the loaddefs.el file.
> I'm not sure what you're saying but I'm saying the behaviour appears to have
> changed.
No doubt, it has changed.
>> >> Is there a way to get the old behaviour. It left problems from
>> >> time to time but I could generally see how to fix them.
>> > How 'bout adding "no-autoloads" annotations to the files you don't
>> > want autoloaded?
> I could do but it's more inconvenient than my previous method.
What can i say: the Makefile is designed to build Emacs, not some local
derivative. This said, I have my own local derivative with about
1MB's worth of changes, and I never needed to silence autoloads, so
I find your situation rather odd. Of course, you can also hack your
local derivative to use different Makefile rules ;-)
Stefan
next prev parent reply other threads:[~2008-06-25 1:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 11:51 Building Emacs Nick Roberts
2008-06-24 13:09 ` Stefan Monnier
2008-06-24 13:26 ` joakim
2008-06-24 21:32 ` Nick Roberts
2008-06-25 1:37 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-18 3:23 Vinicius Latorre
2020-01-18 3:35 ` Jean-Christophe Helary
2020-01-18 3:37 ` Vinicius Latorre
2020-01-18 3:37 ` Noam Postavsky
2020-01-18 3:42 ` Vinicius Latorre
2020-01-18 3:50 ` Jean-Christophe Helary
2020-01-18 3:53 ` Vinicius Latorre
2020-01-18 3:50 ` Noam Postavsky
2020-01-18 3:55 ` Eric Brown
2020-01-19 5:41 ` Paul Eggert
2020-01-19 23:53 ` Vinicius Latorre
2020-01-19 23:56 ` Vinicius Latorre
2020-01-20 0:17 ` Vinicius Latorre
2020-01-20 3:30 ` Eli Zaretskii
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=jwvabhamh9t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=nickrob@snap.net.nz \
/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).