Re: How to install Xemacs on MacOS X ?

> >>>>>> "Pete" == Pete Oster <poster(a)inter.net&gt; writes: > > Pete> Try as I might, I can't come up with any reason to force > Pete> other interested people to have to search for this > Pete> information themselves. > > Thanks for your effort. Forwarding to the developers. Followups > set to xemacs-beta. > > Pete> The comments in square brackets are mine. As you'll see, my > Pete> attempt to build this failed. > > ===== > > build notes for XEmacs 21.5.9 MacOS X Carbon > > Installation notes can be found at: > http://homepage.mac.com/pjarvis/xemacs-21.5.9.html > > > [*** There's also a prebuilt binary here.] > > Use Project Builder 2.0 running on Jaguar, MacOS X v10.2, to > build XEmacs. Project Builder 1.1 also works, but requires some > minor diddling with source and project files. > > [*** If you have the December 2002 Dev Tools, with Project Builder > 2.1, this project doesn't build as is. See below.]

> > > 1. Download and unzip the XEmacs source files. > http://homepage.mac.com/pjarvis/xemacs-carbon-21.5.9.tar.gz > Put the XEmacs folder in a convenient place. > > [*** You can also get the sources via cvs, as described earlier.] > > 2. Fire up /Applications/Utilities/Terminal and run configure > If you have XFree86 (XDarwin) installed, the wrong thing gets built, > > [*** Presumably /usr/X11R6 has to be moved out of the way to > avoid this problem. Anyway that's what I did. Is there a cleaner > way to disable X11 support?]

> > 3. make the terminal version of XEmacs > This creates necessary supporting files: src/config.h, > Installation, ... > Check that the terminal version works > > 3a. Create ~/.xemacs and copy macintosh/init.el into ~/.xemacs > > [*** This init.el isn't in the cvs tree, but you can extract it > from the prebuilt xemacs at pjarvis' site. Obviously you'd want > to merge this into your existing init.el if you have one.] > > 3b. Copy lisp/macintosh/site-start.el to lisp/site-start.el > > 3c. Check again that terminal version works > > 3d. Some xemacs-packages are included. My favorites include: > c-support > cc-mode > debug > dired > ediff > edit-utils > efs > os-utils > prog-modes > psgml > xemacs-base > xemacs-devel > > 3e. Check again that terminal version works > > 4. Modify existing files that need changes > HAVE_CARBON controls Carbon compilation > > [*** The full diff is in CHANGES but I haven't included it here. > It appears as if these patches have already been applied in the > cvs tree.]

> > > 5. Add new files > > [*** The list of new files is in CHANGES but I haven't included it > here. These files already exist in the cvs tree.] > > > 6. make clean and build the terminal version again > Some manual intervention is necessary here. > I still have issues with byte compiling macintosh elisp files > in proper order. > > [*** Given the state of the cvs tree, it's not clear how the > second build differs from the first. In any case I skipped > this step.] > > > 7. Check again that the terminal version works > > 8. Open macintosh/projects/xemacs.pbproj with Project Builder > > 9. Change Project Builder preferences to build XEmacs.app in > macintosh directory > > 10. Build. XEmacs.app should wind up in the macintosh directory. > Unless you play games with config.h, the version built on > 10.2 will not run on 10.1.x. > > [*** I had to remove the existing reference to xemacs.nib and then > re-add that file to get the build to proceed. But I've never used > ProjectBuilder before, so this could be a misunderstanding on my > part. Once past that problem, the compile proceeded without > errors (though with lots of warnings) but the link failed with > multiple definitions of _main and _environ. I'm guessing this is > because I'm using the December 2002 Dev Tools. A similar issue > with the Dec 2002 tools tripped up fsf carbon emacs.]

> > > > [*** This is followed by a list of new files and a unified diff of > changes > to other files.] > > > > -- > > *plonk* >