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,2e5c3d9c5db6eb95 X-Google-Attributes: gid103376,public From: Gautier Subject: Re: Project structure with Gnat Date: 1999/08/04 Message-ID: <37A84689.6F88BA3F@maths.unine.ch>#1/1 X-Deja-AN: 508775193 Content-Transfer-Encoding: 7bit References: <37A81DAB.53D76730@wanadoo.fr> Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-08-04T00:00:00+00:00 List-Id: > An easy way to do it is to cd to the directory in which the .o and .ali > files are to reside, and execute gnatmake from there. > Then.. all one has to do is > gnatmake -I../ -I../ .. etc. > The .o files and the .ali files will be written to the current directory. > The executable will also be written to the current directory, unless > you redirect/rename with the -o gnatmake switch. There is a little problem with that "cd" solution: compile sources that are precisely in the current directory... I vote for a gnatmake switch to deflect all new .ali and .o into ONE directory, without doing "cd" ("cd" complicates the command from an IDE). Turbo / Borland Pascal and surely Delphi does it and it is VERY comfortable! The "gnatmake -i" us already a plus (avoids different versions of .o/.ali laying everywhere) but it "pollutes" the source directories... -- Gautier -------- http://members.xoom.com/gdemont/