Re: Package paths on Cygwin
--- Steven Elliot Harris <seh(a)panix.com> wrote:
Steve Youngs <sryoungs(a)bigpond.net.au> writes:
> But why don't you just build it from source?
I tried and got stuck. I'm not sure I'll have time to figure out how
to build my own XEmacs that works as well as the packaged 21.4.13
does.
Here's what I did:
o Check out 21.5 from CVS.
o Run configure, providing my local installation prefix and no other
arguments, just to see what that would get built.
o Run make.
o Start thinking about all the Cygwin packages I'll need to install to
get this done.
Keep in mind that my Cygwin installation mostly contains library or
runtime packages but not necessarily the corresponding "devel"
packages, for I don't build too many programs from scratch. That may
explain some of the warnings and the failure evident in the build
transcript attached below.
Is there some way to figure out what arguments were provided to
configure in an existing XEmacs build? I'd like to see how the
packaged 21.4.13 was built.
From build-msw-release.sh in the top-level directory:
./configure --with-dragndrop --with-postgresql=no --with-x=no \
--bindir=/usr/local/bin/i686-pc-cygwin --with-site-lisp=yes \
--with-ipv6-cname=no --with-netinstall
However, I've never been able to get it to work without adding the --pdump
option. FWIW, here's the configure options I use:
prefix=/tools/local
./configure --cflags='-g -O' \
--without-x11 \
--with-msw \
--with-dragndrop \
--with-xpm \
--pdump \
--prefix=$prefix \
--site-prefixes=$prefix \
--package-path=$prefix/lib/xemacs/packages
Rick