From mboxrd@z Thu Jan 1 00:00:00 1970 From: psmith@baynetworks.com (Paul D. Smith) To: help-gcc@gnu.org Subject: Re: using make on big Java projects Date: Fri, 31 Dec 1999 22:24:00 -0000 Message-ID: References: <3845C34E.4FFB923A@usa.net> X-SW-Source: 1999-12n/msg00046.html Message-ID: <19991231222400.xj1BaRUL5hBhfSuNJ_aAn6EoPodaRbQlheZ2cGhQJHg@z> %% oneself writes: o> I have just recently started writing makefiles and using make. and o> I want to it on an already existing, very big Java project that o> contains something like 500 files in an elaborate tree structure. o> from the brief but decisive acquaintance I had with make there was o> one thing that became obvious to me, and that is that I had to o> actually put in every file name in the make file. and,if I was o> bored enough, their dependencies. Typically build environments use some sort of automated dependency detection method. No one ever bothers to write header dependencies by hand anymore. There are many solutions for C. I'm not familiar with Java so I can't advise you on that aspect of it. o> my first question is, am I right or wrong. if I'm wrong then how o> can I make make make my whole project with out putting in every o> file name in the makefile. if I'm write, are there any tools out o> there that make this task easier to manage. If you want to find every *.java filename for example, look at $(wildcard ...). If you need something more flexible (every filename in a deep directory structure maybe), try $(shell ...) FILES := $(shell find . -name \*.java -print) -- ------------------------------------------------------------------------------- Paul D. Smith Network Management Development "Please remain calm...I may be mad, but I am a professional." --Mad Scientist ------------------------------------------------------------------------------- These are my opinions---Nortel Networks takes no responsibility for them.