On Nov 27, 2006, at 1:56 PM, MJ Ray wrote:

> Adrian Robert <[EMAIL PROTECTED]> wrote:
>> I meant to send a message out about this last week: I am making a
>> release soon, updated to latest source tree.   [...]
>
> Is there anything that needs to/can be done so that Emacs.app can be
> built easily by package build scripts?  (debian/rules, Compile,  
> emerge)

Hi,

Under GNUstep / Debian, I don't think there is much.  Gürkan Sengün  
has prepared a Debian package and I believe I fixed most build /  
script issues he had to work around.  See http://io.debian.net/~tar/ 
debian/emacs/ .  As far as I know no one has tried packaging for  
other distributions yet.

However, there are two things that need to be improved.  First, this  
build and others currently rely on the script 'nextstep/compile'.  I  
would eventually like to get rid of this script and have the build  
work entirely from the config and makefiles.  Second, a build style  
in which the lisp files and other resources are installed under /usr/ 
local/share/emacs (or /usr/share/emacs) as well as /usr/local/bin,  
etc. should be supported, for convenience of those wishing to  
experiment with different (X and non-X) versions of emacs on their  
systems.

To do this, a configure option could be added: --self-contained=yes  
(the default), and --self-contained=no.

- Running "make" would create nextstep/build/Emacs.app; if --self- 
contained=yes, all of the lisp files, etc. are copied there as now.   
No explicit settings of the PATH variables should be required to do  
this.

- Running "make install" would copy nextstep/build/Emacs.app to / 
Applications (OS X) or ${GNUSTEP_LOCAL_ROOT}/Applications (GNUstep).   
This should be overridable by an --ns-app-install-dir configure  
option.  Additionally, if self-contained=no, it would also install  
the lisp files, etc. based on the --prefix setting.

Implementing these changes would make Emacs.app more approachable for  
packagers and users compiling from source and also greatly ease  
integration of Emacs.app into the GNU Emacs source when that time comes.

Not all of these changes would be trivial: the current nextstep/ 
compile script uses "make install" to create a self-contained  
package.  I'm not sure if there's an easy way to assemble the self- 
contained app without using make's 'install' target.  Perhaps this  
should remain the same, and a new "install-ns-app" target (depending  
on "install") would be added to do the final stage of copying  
nextstep/build/Emacs.app to the final destination (regardless of  
whether 'self-contained' is used).

Let me know if you have thoughts on this approach or want to take a  
stab at doing these mods (after the release).


thanks,
Adrian




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Emacs-app-dev- mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-

Reply via email to