From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,INVALID_DATE, SUBJ_ALL_CAPS autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3f7ddf79b88a134,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1993-03-11 08:04:55 PST Newsgroups: comp.lang.ada Path: sparky!uunet!cs.utexas.edu!mars.tsd.arlut.utexas.edu!bemont From: bemont@tsd.arlut.utexas.edu (Les Bemont) Subject: ADA MAKEFILES? Message-ID: <1993Mar11.155139.20791@titan.tsd.arlut.utexas.edu> Sender: usenet@titan.tsd.arlut.utexas.edu Nntp-Posting-Host: griffin Organization: Applied Research Laboratories, University of Texas at Austin Date: Thu, 11 Mar 1993 15:51:39 GMT Date: 1993-03-11T15:51:39+00:00 List-Id: Hello out there! We're trying to write build scripts for our software project which uses over 1500 files. We're using VADS vers 6.0 (Sun-4 SunOS and UNIX System V/386). To say the least, we are not satisfied with a.make. We have heard of other large projects writing their own makefiles. We haven't had any success using the C makefile philosophy because we can't figure out a generalized dependency rule. We don't really understand how VADS makes its objects. Is there anyone out there who has experience with writing ada makefiles who would be willing to share some info with us? I wish I could be more specific about our needs, but I really don't know where to start. I guess we need to know how to write an ada makefile that would be as flexible and tight as a C makefile. Is it possible? Any info would be greatly appreciated! Please e-mail me. --Les Bemont (bemont@titan.tsd.arlut.utexas.edu) University of Texas at Austin Applied Research Labs -- *************************************************************************** Remember: The Build Police are watching...