From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: "make" in lisp/ not doing The Right Thing?
Date: Wed, 20 Feb 2002 10:15:13 -0500 [thread overview]
Message-ID: <2nu1sc2ni6.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <87sn7w1aah.fsf@cs.utah.edu> (Karra's message of "Wed, 20 Feb 2002 20:15:58 +0530")
Karra <karra@cs.utah.edu> writes:
> Is there any good reason for the following behaviour: _all_ .elc
> files are built from the .el files, even if they are newer than the
> corresponding .el files.
It is because some files depend on macros or inline functions in other
files. It is similar to .c files defending on some .h files. If you
change .h files, you have to recompile .c files. Due to the unknown
dependence, it is safe to build all .elc files. However, if you are
sure that there are no such changes, you can use `make some'.
As to the second patch, you can't use srcdir as the prefix of .elc
files, because .elc files may not locate in the same directory as .el
files. For example, you can put gnus source code in a directory, say
"gnus". To build it for Emacs in another directory, say "gnus-emacs",
run "../gnus/configure --src-dir=../gnus" under directory gnus-emacs.
To build it for XEmacs in the third directory, say "gnus-xemacs", run
"../gnus/configure --src-dir=../gnus --with-xemacs" under directory
gnus-xemacs.
ShengHuo
next prev parent reply other threads:[~2002-02-20 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 14:45 Karra
2002-02-20 15:03 ` Simon Josefsson
2002-02-20 15:03 ` Simon Josefsson
2002-02-20 15:15 ` ShengHuo ZHU
2002-02-20 15:15 ` ShengHuo ZHU [this message]
2002-02-20 15:23 ` ShengHuo ZHU
2002-02-20 15:23 ` ShengHuo ZHU
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 14:45 Karra
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=2nu1sc2ni6.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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.
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 NNTP newsgroup(s).