🚀 go-pugleaf

Make doesn't always like directories (and changing to them).  It is much easier
to create a makefile for each directory, and then write one 'master' makefile
that calls the others (called a recursive makefile; check the O'Reilly book).

Also, did you provide a list of targets?  You may want to add a macro, such as
${CLASSES} in this example:

#Begin makefile
CLASSES = DbKnn.class \
Knn.class

all : ${CLASSES}

%.class : %.java
javac $?
#End makefile

Now you only have to add the class name to the ${CLASSES} macro for each new
class.  IF you want to get fancy, jar the classes using the same technique.

GoodLuck!!

-Brandon



In article <9fc4e2$cko$1@jik.kamens.brookline.ma.us>, Jonathan Kamens says...
>
>In article <sa8snhiepqq.fsf_-_@sun_tong_001.personal.yahoo.com>,
> * Tong * <sun_tong_001@yahoo.com> writes:
>>Here is an example of explicit rule:
>>
>>${CLASSFDIR}/knn/DbKnn.class: knn/DbKnn.java
>>        javac -d ${CLASSFDIR} knn/DbKnn.java
>>
>>${CLASSFDIR}/knn/Knn.class: knn/Knn.java
>>        javac -d ${CLASSFDIR} knn/Knn.java
>>
>>Any idea that can make 'make' work this way? 
>
>I am not sure what the problem is.  The rule I already gave you should
>work just fine:
>
>${CLASSFDIR}/%.class: %.java
>	javac -d ${CLASSFDIR} $<
>
>Note that there's nothing special about slashes as far as '%' is
>concerned -- it's a generic wildcard.  In the examples you gave above,
>it would match "knn/DbKnn" the first time or "knn/Knn" the second time.
>
>Perhaps there's something wrong with your example?