On 28 Apr 2003 16:32:34 +0200, Adrian Aichner wrote:
Hello Ben, I have now verified with latest CVS head that
http://list-archive.xemacs.org/xemacs-patches/200301/msg00085.html
is not to blame from this breakage I'm seeing.
I am suspecting breakage between xemacs.mak and config.inc.
Ben, have you tested your latest changes without using either
BUILD_DIR or SOURCE_DIR?
I use neither and get the problem described below.
Is it correct to conditionalize the PATH_* settings on
SEPARATE_BUILD?
xemacs.mak has this:
PATH_DEFINES=-DPATH_PREFIX=\"$(PATH_PREFIX)\"
!if $(SEPARATE_BUILD)
PATH_DEFINES=$(PATH_DEFINES) -DPATH_LOADSEARCH=\"$(LISP:\=\\)\" -
DPATH_DATA=\"$(ETC:\=\\)\" -DPATH_INFO=\"$(INFO:\=\\)\"
!endif
Please advise,
Adrian
Short term workaround on Win <ALL> (I am using XP and encountered same behavior) is
to open up any/all shortcuts to xemacs and put the location of the xemacs.exe into the
"Start In' field. BTW, 21.5.11 did not exhibit this problem. Breakage introduced
in some change for 21.5.12.
--
Matthew O. Persico