Re: Binary distributions [ was Re: [PROPOSAL] fix for bad Xrefs ... ]

Darryl Okahata wrote: I've glanced at doing this because I thought that it would be a good idea too. Installshield is the mswindows way of doing things, so using it would make mswindows users feel comfortable. It could also add an XEmacs icon to the "Start" menu, associate .el files with XEmacs etc. Using InstallShield also has the big advantage that we could set EMACSPACKAGEPATH and maybe some other variables in the user's registry at install time. This would mean that the user wouldn't have to set environment variables in order to override the compile-time defaults. (This is particularly pertinent to the package path; I haven't been able to force nmake/cl to accept "C:/Program Files/xemacs/packages" as a compile-time default package path because of the space in that pathname, and that is probably where the user would want to keep packages). A sensible install tree for XEmacs on mswindows might look like: PROGS\XEmacs\ packages\ XEmacs-21.0\ bin info lisp where PROGS should default to "C:\Program Files". Unfortunately, XEmacs currently fails to cope with such a layout because it expects a UNIX-style install tree; it can't find it's root directory (paths-find-emacs-roots fails) and it also can't find any of the exec, info or data directories. Jonathan. -- Jonathan Harris | jhar(a)tardis.ed.ac.uk London, England | Jonathan-Harris(a)psion.com