unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: help with makefile command line
Date: Sat, 29 Mar 2008 09:33:15 -0600	[thread overview]
Message-ID: <fslnfq$u99$1@ger.gmane.org> (raw)
In-Reply-To: <c33ub5-k56.ln1@invalid.net>

stan wrote:
> Richard G Riley wrote:
>> "Balaji V. Iyer" <bviyer@ncsu.edu> writes:
>>
>>> Hello Everyone,
>>>     I use the compile option extenstively in emacs. When I type "M-x
>>> compile" the default line is "make -k" Many times I do not have a make
>>> file thus I would lke the default line to be
>>>  
>>> "gcc -ansi -O4 -Wall <c_source_file>"
>>>  
>>> How do I do this?
>>>  
>>> I tried the following command but it doesn't seem to work (If anyone
>>> have a better idea please let me know).
>>>  
>>> (function
>>>  (lambda ()
>>>    (unless (or (file-exists-p "makefile")
>>>                (file-exists-p "Makefile"))
>>>      (setq compile-command
>>>            (concat "gcc -Wall -O3 -o"
>>>                    (file-name-sans-extension (file-name-nondirectory
>>> buffer-file -name))
>>>                    " "
>>>                    (file-name-nondirectory buffer-file-name))))))
> <snip>
> 
> Seems like it might be easier to write a makefile :) 

You don't need to write a Makefile, because make has built-in rules that
handle this.

(add-hook 'c-mode-hook
	  (lambda ()
	    (set (make-local-variable 'compile-command)
		 (format "make %s"
			 (file-name-sans-extension
			  (file-name-nondirectory buffer-file-name))))))

Just set the CC=gcc and CFLAGs="-Wall -O3" environment variables, and voila!

-- 
Kevin Rodgers
Denver, Colorado, USA





  parent reply	other threads:[~2008-03-29 15:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9409.1206451688.18990.help-gnu-emacs@gnu.org>
2008-03-27 15:36 ` help with makefile command line step
2008-03-27 17:28 ` Richard G Riley
2008-03-28  2:51   ` stan
2008-03-28  3:01     ` Richard G Riley
2008-03-28  7:11       ` stan
2008-03-28 12:57         ` Richard G Riley
2008-03-28 20:33           ` stan
2008-03-29 13:18             ` Richard G Riley
2008-03-29 15:33     ` Kevin Rodgers [this message]
2008-03-25 13:09 Balaji V. Iyer
2008-03-25 14:04 ` William Xu
2008-03-26  4:19 ` Eli Zaretskii
2008-03-26  4:25   ` Mike Mattie
2008-03-26  4:42   ` Mike Mattie
2008-03-26  4:57     ` Mike Mattie
2008-03-26 16:20 ` Nikolaj Schumacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='fslnfq$u99$1@ger.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).