Re: Dependencies in lisp/

[Kenichi Handa]

Eli Zaretskii <address@hidden> writes:
> On Tue, 27 Nov 2001, Kenichi Handa wrote:

>>  We should somehow force bootstrapping if something is
>>  changed in mule-conf.el to avoid this kind of error in the
>>  future.

>>  We should somehow force bootstrapping if something is
>>  changed in mule-conf.el to avoid this kind of error in the
>>  future.

> I think bootstrapping is an overkill;

Yes.  We don't have to compile *.o.  But...

> all you need is to byte-compile mule-conf and dump Emacs,
> right?

No.  We don't have to byte-compile mule-conf.el, but have to
byte-compile the other modified files by a new Emacs that is
built with the new mule-conf.el.  That is the difficult
part.  We may be able to load several Emacs Lisp files in
the old temacs and ask it to byte-compile them.

> There are a few similar problems in the lisp directory.  For example,
> changes in derived.el or easy-mmode.el sometimes require to recompile
> all the *.el files which use define-derived-mode or define-minor-mode.

> I think Someone(tm) should figure out such dependencies between Lisp
> files and update lisp/Makefile.in accordingly.

For derived.el and easy-mmode.el, grepping some patterns in
Emacs Lisp files will figure out which files depends on
them.  But, in the case of mule-conf, it's almost
impossible.  We can't figure out which file contains a newly
introduced characters.  So, the safe way is to byte-compile
all files newer than mule-conf.el (this method assumes that
when we install changes to mule-conf.el and some other files
at the same time, we always install the change to
mule-conf.el at first).

---
Ken'ichi HANDA
address@hidden