[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "make autoloads" signals an error
From: |
Eli Zaretskii |
Subject: |
Re: "make autoloads" signals an error |
Date: |
Thu, 02 Jun 2022 15:05:35 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: wavexx@thregr.org, emacs-devel@gnu.org
> Date: Thu, 02 Jun 2022 13:59:40 +0200
>
> > . if you put the *.elc files in the build tree, you need to adjust
> > load-path, since some of the files (the ones we don't
> > byte-compile) will be in the source tree, and others in the build
> > tree
>
> Hm, yes. But... would just prepending the build/lisp/* directories to
> load-path fix that issue? I.e., use the .elc files from build/lisp and
> fall back on lisp-directory otherwise?
How do you prepend it? The setting of load-path is done early during
startup, see init_lread.
- Re: "make autoloads" signals an error, (continued)
- Re: "make autoloads" signals an error, Ergus, 2022/06/01
- Re: "make autoloads" signals an error, Ergus, 2022/06/01
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Yuri D'Elia, 2022/06/02
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Eli Zaretskii, 2022/06/02
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Eli Zaretskii, 2022/06/02
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error,
Eli Zaretskii <=
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Eli Zaretskii, 2022/06/03
- Re: "make autoloads" signals an error, Andreas Schwab, 2022/06/02
- Re: "make autoloads" signals an error, Lars Ingebrigtsen, 2022/06/02
- Re: "make autoloads" signals an error, Eli Zaretskii, 2022/06/01