Re: Module path initialization

Jerry> 1) The function paths-find-emacs-roots, if given an Jerry> invocation-directory argument that is outside of the XEmacs Jerry> source tree, returns the root of the build tree, but NOT Jerry> the root of the source tree. Is that desirable behavior? Yes. Otherwise it would confound an existing in-source build with a separate build directory build. This is not a problem for Lisp and Info (we hope), thus the links, but in principle the build tree should contain its own copy of all generated files. Jerry> That is, would it be wrong if it returned the list Jerry> (build-tree source-tree)? Ie, yes. Right, Michael? 2) When building outside of the source tree, configure sets up build directories and links to things inside the source tree. However, it neither creates a "modules" directory nor links to the one in the source tree. Is that wrong? Yes. It should either copy the modules tree or link to it. Martin says "XEmacs knows everything the modules needs to know, ask XEmacs about configuration stuff." If that's true, then it's quite likely that the modules will be XEmacs-build-dependent, and the tree should be _copied_. If modules should be independent of the xemacs binary build, then the tree should be _linked_ and we should be looking for dependencies on the build process, considering them to be bugs. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."