xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk-Willem van Gulik <di...@webweaving.org>
Subject Makefile's
Date Thu, 25 Nov 1999 11:26:40 GMT

I am looking at various makefile options, gmake vs make vs Ant. Is there 
a good reason why a lot of OS java author's seem prefer

	1.	to simply compile everything in one javac statement
		which has been CD's to the right output 
		directory. Regardless of wether all java files need
		to be recompiled.
over
	2.	compile everhting and use a -o/-d/-xxx output
		specifier
over
	3.	defined dependencies and do it file by file
		instead of all, and only when needed

Is there a good reason ? Are dependencies too hard ? Or do (some)
compiler's work this out themselfes well enough ?

And secondly, why is there such a strong desire to move the *.class
file's far away from the source ?

If anyone could help me understand ?

Dw

(i.e. from make:)

----
something:
	( cd somewhre; $(JAVAC) $(JAVACFLAGS) $(SRCS))
---

over

----
something:
	$(JAVAC) $(JAVACFLAGS) $(DIRFLAG) somwhere $(SRCS)
----

over

----
OBJS = ${SRCS:.java=.class}

.SUFFIXES : .java .class

something: $(OBJS)
	
.java.class
	$(JAVAC) $(JAVACFLAGS) $(DIFGLAG) somwhere/$@ $<
	# optional @mv something
---




Mime
View raw message