Hi David, On Feb 13, 2008 2:59 PM, David Reitter <[EMAIL PROTECTED]> wrote:
> Have a look at mac.c. I find it easiest to work with the GNU Emacs > source code directly when doing C level changes. the "make-package" > script is okay for your initial build, but use --build-in-place as > option so it wont' re-build the whole thing every time you compile. So I've just built the 2008 src tarball for the first time, and was poking through the source code while it was building. I did a make-package --build-in-place from inside the emacs/mac directory. The build went okay, but now I'm a little unclear what the typical hack/rebuild/debug cycle looks like. I can't launch the Emacs executable directly from the looks of it (Warning: arch-dependent data dir (/usr/local/libexec/emacs/22.1.50/i386-apple-darwin9.1.0/) does not exist), but I bet that using the .dmg and doing a full-blown install is the wrong way to go about it. Any suggestions? I'll comb through the list a bit more to see if I can glean anything. Thanks for helping out a newbie emacs hacker, Joel -- "Make sense who may. I switch off." -- Beckett --~--~---------~--~----~------------~-------~--~----~ Carbon Emacs User Group http://groups.google.com/group/carbon-emacs?hl=en -~----------~----~----~----~------~----~------~--~---
