On Wed, 29 May 2002, andy(a)xemacs.org wrote:
Maybe Mike Sperber could comment on this. I've never understood
compile time paths get put into the executable. And I never figured out
where they got put.
when you load a .elc file the path the file name goes into
load-history. If you use an absolute path, eg
then the absolute path gets put into load-history. Those absolute
paths will work *only* on the machine where you built the xemacs image.
Files that are dumped into the xemacs image are loaded with absolute
pathnames - eg
(caar (nthcdr (- (length load-history) 5) load-history)) -->
"/opt/sfw/lib/xemacs-21.4.6/lisp/find-paths.elc" (for me)