Re: Recent changes to xemacs.mak
Adrian Aichner <[email protected]>
| Newsgroups | gmane.emacs.xemacs.windows |
|---|---|
| Organization | The XEmacs Project |
| Message-ID | <[email protected]> |
>>>>> "Mike" == Mike Alexander <[email protected]> writes: Hi Mike, what's up? I found stranded mail in my www.xemacs.org adrian mailbox. Have these issues been resolved? Best regards, Adrian Mike> I like the new support for multiple build trees from a single source Mike> tree on Windows. I've had a kluge like that for ages, but Ben's Mike> version is much better. Mike> I have noticed a couple of things that aren't quite right, or at least Mike> are a bit confusing. For one thing, relative paths for BUILD_DIR or Mike> SOURCE_DIR don't work right. I've been using "..\Debug" and Mike> "..\Release" to build both a debug and release build from the same Mike> source tree and had to change the make file a bit to always cd back to Mike> the original directory after each cd somewhere else so subsequent file Mike> references or cd's based on BLDROOT or SRCROOT work right. I can Mike> submit a patch for that if it's necessary. Mike> I also got in to trouble when I built a copy of XEmacs using the Mike> "install" target on one machine then copied the resulting install tree Mike> to another machine. It happened that the second machine had an old Mike> copy of the build tree on it. Because xemacs.mak defines Mike> PATH_LOADSEARCH and PATH_DATA if SEPARATE_BUILD is true, the copy on Mike> the second machine started using lisp files from the old build tree. Mike> It got itself very confused when it used a version of cus-face.el from Mike> last September. I'm not quite sure what the best fix for this is Mike> since I'm not really sure why xemacs.mak defines PATH_LOADSEARCH and Mike> PATH_DATA. I fixed it easily enough by renaming the build tree on the Mike> second machine, but this could hit someone else someday. Mike> One other thing is that XEmacs seems to think that the DOC file should Mike> be in $(INSTALL_DIR)\lib-src but the install target puts it in Mike> $(INSTALL_DIR)\$(EMACS_CONFIGURATION). In fact the install target Mike> doesn't create lib-src at all and XEmacs complains about the install Mike> tree if it doesn't exist. Mike> Mike Alexander <mailto:[email protected]> Mike> Arbortext, Inc. +1-734-997-0200 -- Adrian Aichner mailto:[email protected] http://www.xemacs.org/