Re: java and M-x compile

Re: java and M-x compile

[kgold]

LENNART BORGMAN <lennart.borgman.073@student.lu.se> writes: By default
> M-x compile RET runs "make -k". The emacs manual says that this
> should be good for most simple programs. It does not seem to be very
> good for a simple java program.
> 
> At least not for me, using GNU Make 3.80 on W2k. Is there something
> I am missing? (Of course I can still compile java in Emacs, but
> could make -k work by default, or does it need a makefile?)

It might mean that make typically comes with standard defaults, so
e.g., knows to run a C compiler on .c files.

However, most users will create a custom makefile relevant to their
project.

-- 
Ken Goldman   kgold@watson.ibm.com   914-784-7646

Re: java and M-x compile

[Peter Dyballa]

Am 30.09.2005 um 13:07 schrieb kgold:

> It might mean that make typically comes with standard defaults, so
> e.g., knows to run a C compiler on .c files.
>

Even when you know how to enter a train: how will you be able to arrive 
at your target destination when you neither know it nor how many times 
and where you have to change into which other trains?

A makefile is needed!

--
Greetings

   Pete

When confronted with actual numbers, a mathematician is at a loss.  
(Steffen Hokland)

Re: java and M-x compile

[isuy]

You probably want JDEE.

http://www.jdee.sunsite.dk


LENNART BORGMAN <lennart.borgman.073@student.lu.se> writes:

> By default M-x compile RET runs "make -k". The emacs manual says that this should be good for most simple programs. It does not seem to be very good for a simple java program. 
> 
> At least not for me, using GNU Make 3.80 on W2k. Is there something I am missing? (Of course I can still compile java in Emacs, but could make -k work by default, or does it need a makefile?)

Re: java and M-x compile

[isuy]

Sorry, try this instead.

http://jdee.sunsite.dk/


isuy <isuy@sbcglobal.net> writes:

> You probably want JDEE.
> 
> http://www.jdee.sunsite.dk
> 
> 
> LENNART BORGMAN <lennart.borgman.073@student.lu.se> writes:
> 
> > By default M-x compile RET runs "make -k". The emacs manual says that this should be good for most simple programs. It does not seem to be very good for a simple java program. 
> > 
> > At least not for me, using GNU Make 3.80 on W2k. Is there something I am missing? (Of course I can still compile java in Emacs, but could make -k work by default, or does it need a makefile?)

Re: java and M-x compile

[Lennart Borgman]

Oh yes, thanks, I want to use JDEE of course. I just wanted to know how 
things were supposed to work first.


isuy wrote:

>Sorry, try this instead.
>
>http://jdee.sunsite.dk/
>
>
>isuy <isuy@sbcglobal.net> writes:
>
>  
>
>>You probably want JDEE.
>>
>>http://www.jdee.sunsite.dk
>>
>>
>>LENNART BORGMAN <lennart.borgman.073@student.lu.se> writes:
>>
>>    
>>
>>>By default M-x compile RET runs "make -k". The emacs manual says that this should be good for most simple programs. It does not seem to be very good for a simple java program. 
>>>
>>>At least not for me, using GNU Make 3.80 on W2k. Is there something I am missing? (Of course I can still compile java in Emacs, but could make -k work by default, or does it need a makefile?)
>>>      
>>>

Re: java and M-x compile

[Nick Roberts]

> > It might mean that make typically comes with standard defaults, so
> > e.g., knows to run a C compiler on .c files.
> >

> Even when you know how to enter a train: how will you be able to arrive 
> at your target destination when you neither know it nor how many times 
> and where you have to change into which other trains?

> A makefile is needed!

I don't know about trains but on GNU/Linux or Unix if you type:

make myprog

and you have an executable called myprog.c in that directory, make will
find and compile it:

nickrob/34 make myprog
cc     myprog.c   -o myprog
nickrob/35

Nick

java and M-x compile

[LENNART BORGMAN]

By default M-x compile RET runs "make -k". The emacs manual says that this should be good for most simple programs. It does not seem to be very good for a simple java program. 

At least not for me, using GNU Make 3.80 on W2k. Is there something I am missing? (Of course I can still compile java in Emacs, but could make -k work by default, or does it need a makefile?)

Re: java and M-x compile

[Peter Dyballa]

Am 30.09.2005 um 11:37 schrieb LENNART BORGMAN:

> but could make -k work by default, or does it need a makefile?

make needs a makefile.

--
Greetings

   Pete

The future will be much better tomorrow.
   -- George W. Bush

Re: java and M-x compile

[Lennart Borgman]

Peter Dyballa wrote:

>
> Am 30.09.2005 um 11:37 schrieb LENNART BORGMAN:
>
>> but could make -k work by default, or does it need a makefile?
>
>
> make needs a makefile.

Thanks Pete, that seems reasonable. I do not know make very well so I 
wondered if there were some builtin defaults. This little excerpt from  
Info (emacs) Compilation made me think that:

  "For the first `M-x compile', the default
  is `make -k', which is correct most of the time for nontrivial
  programs.  (*Note Make: (make)Top.) "

What does it mean then? Of course if there is a Makefile then "make -k" 
is correct for most nontrivial programs. At least I hope so ;-)

Then for trivial programs I obviously should try something else. Even 
though it is not true it feels like I have to know more to do simple 
things...

I think I will test something like smart-compile.el or mode-compile.el 
then. Have anyone tried to compare them?

Re: java and M-x compile

[Lee Sau Dan]

>>>>> "Peter" == Peter Dyballa <Peter_Dyballa@Web.DE> writes:

    Peter> Am 30.09.2005 um 11:37 schrieb LENNART BORGMAN:

    >> but could make -k work by default, or does it need a makefile?

    Peter> make needs a makefile.

No.   GNUmake  doesn't  require  a  Makefile.  It  has  default  rules
built-in, so that it can handle the trivial cases without a Makefile.

e.g. you  have a source  file called xyz.cc  and you type  "make xyz".
GNUmake will automatically  invoke "g++ -o xyz xyz.cc"  to compile it.

Behind the scene, GNUmake applies the default rule:
        %: %.cc
        #  commands to execute (built-in):
                $(LINK.cc) $^ $(LOADLIBES) $(LDLIBS) -o $@

where 
        LINK.cc = $(CXX) $(CXXFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH)
        CXX = g++
and all other variables that occurred above undefined.

This makes it possible  to override certain behaviours without writing
a Makefile.  e.g. "make  CXX=my_c++_compiler xyz" will compile it with
"my_c++_compiler"  instead  of "g++".   I  most  often  use "make  xyz
CXXFLAGS=-O3\  -Wall LDFLAGS=-s"  to compile  an  optimized executable
without debug symbols.

No makefiles are needed for such a simple scenario.


You can have a look at the default rule of GNUmake with "make -p -n".



-- 
Lee Sau Dan                     李守敦                          ~{@nJX6X~}

E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee