all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: bug-cc-mode@gnu.org, acm@muc.de,
	Alan Mackenzie_JWA <alan.mackenzie_jwa@nxp.com>,
	emacs-devel@gnu.org
Subject: Re: Compilation order. Help with makefiles, please!
Date: Thu, 30 Aug 2007 15:45:56 -0400	[thread overview]
Message-ID: <jwvodgoolj4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1IQeF8-0003Ov-6Z@fencepost.gnu.org> (Richard Stallman's message of "Thu\, 30 Aug 2007 03\:15\:06 -0400")

> That is a valid argument.  I guess we do need to put specific files in
> lisp/Makefile.in.  I wish it were not necessary, but it is.

An "easy" solution is to prefer reading the newer .el files rather than the
older .elc when `requiring' a file during byte-compilation.  This way, in
the example, if cc-engine.el is compiled before cc-langs.el, it's still OK
because it will load the new cc-langs.el rather than the oild cc-langs.elc.


        Stefan

  reply	other threads:[~2007-08-30 19:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  9:57 Compilation order. Help with makefiles, please! Alan Mackenzie_JWA
2007-08-30  7:15 ` Richard Stallman
2007-08-30 19:45   ` Stefan Monnier [this message]
2007-08-31  7:34     ` Richard Stallman
2007-08-31  8:57       ` Alan Mackenzie_JWA
2007-08-31 14:16         ` Stefan Monnier
2007-09-01  4:06         ` Richard Stallman
2007-10-05 21:54   ` Compilation order. Tentative patch Alan Mackenzie
2007-10-06  5:38     ` Mathias Megyei
2007-10-07  0:31     ` Richard Stallman
     [not found] <E1IMYuS-00059J-B8@fencepost.gnu.org>
2007-08-26  9:38 ` Compilation order. Help with makefiles, please! Alan Mackenzie
2007-08-26 10:28   ` Michaël Cadilhac
2007-08-26 10:55     ` Alan Mackenzie
2007-08-26 22:46   ` Richard Stallman

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=jwvodgoolj4.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acm@muc.de \
    --cc=alan.mackenzie_jwa@nxp.com \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.