Re: Packages and Building XEmacs from CVS
Alastair Burt <burt(a)dfki.de> writes:
Dear beta mailing listers,
I am still having trouble trying to build XEmacs 20.1 from CVS. I would
prefer to build from CVS, because eventually I would like to add x-symbol
to CVS tree.
I configure like this:
./configure --prefix=/home/burt/lib/xemacs
--with-mule--package-path="~/.xemacs::/home/burt/lib/xemacs/lib/xemacs/mule-packages:/home/burt/lib/xemacs/lib/xemacs/xemacs-packages"
The easiest way to do this is to take advantage of the fact that a
local package hierarchy will override the compiled-in package path.
You basically need to create a minimal package hierarchy somewhere and
then symlink it in the top-level XEmacs source directory.
I've put a tarball of my current set of build-from-scripts on the FTP
site:
ftp://ftp.xemacs.org/pub/xemacs/beta/build-scripts.tar.gz
They assume that you have a directory structure that contains both
CVS'ed XEmacs core sources and package sources in the same directory
and are oriented towards building things for distribution, but they
will show you the procedure for building (almost[1]) totally from scratch.
Footnotes:
[1] You need an existing bytecompiled copy of the mule-base package
for the first phase, but it gets re-bytecompiled from current sources
later on.