[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]
byte compiling
- To: "James R. Van Zandt" <jrv@xxxxxxxxxxx>
 
- Subject: byte compiling
 
- From: "T. V. Raman" <raman@xxxxxxxxxxx>
 
- Date: Mon, 31 May 1999 14:21:36 -0700 (PDT)
 
- In-Reply-To: <m10oUte-0006IpC@xxxxxxxxxxx>
 
- Old-Return-Path: <raman@xxxxxxxxxxx>
 
- Reply-To: raman@xxxxxxxxxxx
 
- Resent-Date: Mon, 31 May 1999 17:22:17 -0400 (EDT)
 
- Resent-From: emacspeak@xxxxxxxxxxx
 
- Resent-Message-ID: <"FFU02B.A.tFF.91vU3"@hub>
 
- Resent-Sender: emacspeak-request@xxxxxxxxxxx
 
I do not recommend this method of compiling --
it will introduce inadvertant dependencies between the .el
files as they are compiled with  resulting bugs that might
prove hard to locate.
The current build technique builds each .el file in a clean
environment.
>>>>> "James" == James R Van Zandt <jrv@xxxxxxxxxxx> writes:
    James> Dr. Raman -
    James> Your Makefile runs Emacs separately to byte
    James> compile each elisp file.  I have found that
    James> several other Debian packages use a different
    James> method of byte-compiling Emacs add-ons: They run
    James> Emacs once and byte compile all the files.  I
    James> have adapted the latter method to Emacspeak,
    James> using approximately the following commands:
    James> FLAGS="-q -batch -l path.el -l
    James> emacspeak-load-path.el -f batch-byte-compile"
    James> FILES=`echo *.el` cat << EOF > path.el (setq
    James> load-path (cons "." load-path)
    James> byte-compile-warnings nil) EOF emacs ${FLAGS}
    James> ${FILES}
    James> This appears to offer several advantages: It runs
    James> in about half the time.  It generates about one
    James> third of the output.  It does not generate
    James> warnings about symbols not known to be defined.
    James> Is there some disadvantage to byte compiling this
    James> way?  Otherwise, you might consider setting the
    James> Makefile up this way.
    James> For reference, I believe these are the relevant
    James> lines from the Makefile:
    James> BATCH = -batch -q -no-site-file COMPILE = -eval
    James> "(setq byte-compile-dynamic t)" -f
    James> batch-byte-compile
    James> %.elc: %.el $(EMACS) $(BATCH) -l
    James> $(CWD)/emacspeak-load-path $(COMPILE) $(CWD)/$<
    James> 			   - Jim Van Zandt
-- 
Best Regards,
--raman
      Adobe Systems                 Tel: 1 408 536 3945   (W14-128)
      Advanced Technology Group     Fax: 1 408 537 4042 
      W14-128 345 Park Avenue     Email: raman@xxxxxxxxxxx 
      San Jose , CA 95110 -2704     Email:  raman@xxxxxxxxxxx
      http://labrador.corp.adobe.com/~raman/        (Adobe Intranet)
      http://cs.cornell.edu/home/raman/    (Cornell)
----------------------------------------------------------------------
    Disclaimer: The opinions expressed are my own and in no way should be taken
as representative of my employer, Adobe Systems Inc.
____________________________________________________________
-----------------------------------------------------------------------------
       To unsubscribe or change your address send mail to
"emacspeak-request@xxxxxxxxxxx" with a subject of "unsubscribe" or "help"
   
Emacspeak Files |
Subscribe |
Unsubscribe