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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b5f7c3673f6a6b92 X-Google-Attributes: gid103376,public From: tp@odn.de (Thomas Preymesser) Subject: Re: Optimal Compilation Desired Date: 1998/12/02 Message-ID: <366464fc.10225424@news.nuernberg.odn.de>#1/1 X-Deja-AN: 417962829 References: <365B5C3D.E593F179@hiwaay.net> Organization: ODN Onlinedienst Nordbayern GmbH Newsgroups: comp.lang.ada Date: 1998-12-02T00:00:00+00:00 List-Id: On Tue, 24 Nov 1998 19:24:13 -0600, "Anthony E. Glover" wrote: >Does anyone have a script or command line that will optimally compile >all code in a given directory, i.e. don't compile specs that have bodies >or separates. I have a library of reuse code that does not contain any >kind of main and I just want to compile everything. I currently compile >*.ads and then *.adb, but this of course attempts to compile specs >that don't need to be compiled. why don't you use some sort of make-program, which will exactly compile what must be compiled and nothing more? -Thomas