Management C Project Files with Emacs?

Management C Project Files with Emacs?

[Daniel]

Hi,

If I want to compile a large project like Linux Kernel, I don't know
how I can use emacs.

1. For example, if I modified <linux>/drivers/usb/core/hcd.c with
emacs, then How I can compile linux kernel by M-x compile command?
When I do the command, it is saying that there is no makefile. So, I
use "M-x compile RET make -f /usr/src/linux/makefile", but it
complains that there is no definition of u32 etc. How do I do that?

2. Whenever opening a file, it seems that emacs change current
directory. So, I cannot simply type "M-x compile RET make". Is there
anyway to have emacs to stick on specific directory?

Re: Management C Project Files with Emacs?

[Peter Dyballa]

Am 28.03.2007 um 21:15 schrieb Daniel:

> If I want to compile a large project like Linux Kernel, I don't know
> how I can use emacs.

I remember that I was using rpm to build the kernel in shell ... and  
when you rename this buffer (to *kernel* for example), you can create  
a new *shell* buffer.

--
Greetings

   Pete      <\
              _\     O  _
             |o \  _\\_/-\='
_____________(_)|-(_)  (_)___________________________________

Re: Management C Project Files with Emacs?

[Daniel]

On Mar 28, 1:28 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 28.03.2007 um 21:15 schrieb Daniel:
>
> > If I want to compile a large project like Linux Kernel, I don't know
> > how I can use emacs.
>
> I remember that I was using rpm to build the kernel in shell ... and
> when you rename this buffer (to *kernel* for example), you can create
> a new *shell* buffer.
>
> --
> Greetings
>
>    Pete      <\
>               _\     O  _
>              |o \  _\\_/-\='
> _____________(_)|-(_)  (_)___________________________________

Thank you for your response, but that does not seem to be not what I
want.

First, the kernel compile is just for example to show for building big
project.
Second, I don't understand how I rename the buffer name, and how
creating a new *shell* buffer would help me out to compile.

Daniel.

Re: Management C Project Files with Emacs?

[Peter Dyballa]

Am 28.03.2007 um 22:59 schrieb Daniel:

> First, the kernel compile is just for example to show for building big
> project.

What about X11R7.2? Less bleeding edge would be X11R7.1. The latter  
one takes for me a few hours – is this big enough? (Editing the  
build.sh script, or better a working copy of it, you can reduce the  
amount of X clients, libraries, and servers that get compiled.)

> Second, I don't understand how I rename the buffer name, and how
> creating a new *shell* buffer would help me out to compile.

	M-x rename-buffer RET new name RET
	M-x shell RET

A new *shell* buffer would allow you to do other things in it while  
the kernel is compiled in the previous one ...

--
Greetings

   Pete

What’s the difference between OS X and Vista?

Microsoft employees are excited about OS X…

Re: Management C Project Files with Emacs?

[Colin S. Miller]

Daniel wrote:
> Hi,
> 
> If I want to compile a large project like Linux Kernel, I don't know
> how I can use emacs.
> 
> 
> 2. Whenever opening a file, it seems that emacs change current
> directory. So, I cannot simply type "M-x compile RET make". Is there
> anyway to have emacs to stick on specific directory?
> 

These easiest way to do this is to change the compile line to

cd /path/to/src/ && make -f Makefile ALL


HTH,
Colin S. Miller


-- 
Replace the obvious in my email address with the first three letters of the hostname to reply.

Re: Management C Project Files with Emacs?

[Daniel]

On Mar 28, 2:50 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 28.03.2007 um 22:59 schrieb Daniel:
>
> > First, the kernel compile is just for example to show for building big
> > project.
>
> What about X11R7.2? Less bleeding edge would be X11R7.1. The latter
> one takes for me a few hours - is this big enough? (Editing the
> build.sh script, or better a working copy of it, you can reduce the
> amount of X clients, libraries, and servers that get compiled.)
>
> > Second, I don't understand how I rename the buffer name, and how
> > creating a new *shell* buffer would help me out to compile.
>
>         M-x rename-buffer RET new name RET
>         M-x shell RET
>
> A new *shell* buffer would allow you to do other things in it while
> the kernel is compiled in the previous one ...
>
> --
> Greetings
>
>    Pete
>
> What's the difference between OS X and Vista?
>
> Microsoft employees are excited about OS X...

Thank you, Pete. X11R7.1 or 2 could be big project enough.
Thank you for the response, and now I could get how to rename buffer.

Re: Management C Project Files with Emacs?

[Daniel]

On Mar 28, 4:15 pm, "Colin S. Miller" <no-spam-
thank-...@csmiller.demon.co.uk> wrote:
> Daniel wrote:
> > Hi,
>
> > If I want to compile a large project like Linux Kernel, I don't know
> > how I can use emacs.
>
> > 2. Whenever opening a file, it seems that emacs change current
> > directory. So, I cannot simply type "M-x compile RET make". Is there
> > anyway to have emacs to stick on specific directory?
>
> These easiest way to do this is to change the compile line to
>
> cd /path/to/src/ && make -f Makefile ALL
>
> HTH,
> Colin S. Miller
>
> --
> Replace the obvious in my email address with the first three letters of the hostname to reply.

Hi Colin,

That is good idea.

Moreover, I also find I could make it this:
     M-x make RET make -C /usr/src/linux RET
Above make option indicates the root directory for the make no matter
where I am in.

Thank you guys, it was helpful to me.

Re: Management C Project Files with Emacs?

[Hadron]

"Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk> writes:

> Daniel wrote:
>> Hi,
>>
>> If I want to compile a large project like Linux Kernel, I don't know
>> how I can use emacs.
>>
>>
>> 2. Whenever opening a file, it seems that emacs change current
>> directory. So, I cannot simply type "M-x compile RET make". Is there
>> anyway to have emacs to stick on specific directory?
>>
>
> These easiest way to do this is to change the compile line to
>
> cd /path/to/src/ && make -f Makefile ALL
>
>
> HTH,
> Colin S. Miller

This would be really limiting at a later date. Better to open the
makefile or the c file you are interested in so emacs deafults to the
right directory when you then make.

Here is my compile command:

(defun my-compile ()
  (lambda ()
    (unless (file-exists-p "Makefile")
      (set (make-local-variable 'compile-command)
	   ;; emulate make's .c.o implicit pattern rule, but with
	   ;; different defaults for the CC, CPPFLAGS, and CFLAGS
	   ;; variables:
	   ;; $(CC) -c -o $@ $(GTKFLAGS) $(CPPFLAGS) $(CFLAGS) $<
	   (let ((file (file-name-nondirectory buffer-file-name)))
	     (format "%s -o %s %s %s %s %s"
		     (or (getenv "CC") "gcc")
		     (file-name-sans-extension file)
		     (or (getenv "GTKFLAGS") "")
		     (or (getenv "CPPFLAGS")"-DDEBUG=9")
		     (or (getenv "CFLAGS") "-std=c99 -pedantic -Wall -Werror -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wconversion  -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Winline -g")
		     file)))))
  )



--