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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4ad87aeffb1e31d3 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-30 00:53:35 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!priapus.visi.com!news-out.visi.com!hermes.visi.com!newsfeed.esat.net!lnewspeer01.lnd.ops.eu.uu.net!emea.uu.net!news!not-for-mail From: Nige Newsgroups: comp.lang.ada Subject: Re: How to Build Existing Code Using Apex Date: Tue, 30 Apr 2002 08:55:59 +0100 Organization: Thales Message-ID: <3CCE4E0F.A1B4BC10@uk.thalesgroup.com> References: NNTP-Posting-Host: 172.21.150.55 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: rdel.co.uk 1020153213 20938 172.21.150.55 (30 Apr 2002 07:53:33 GMT) X-Complaints-To: postmaster@uk.thalesgroup.com NNTP-Posting-Date: 30 Apr 2002 07:53:33 GMT X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4m) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ada:23260 Date: 2002-04-30T07:53:33+00:00 List-Id: maiale wrote: > > Hi, > > I am new to ada/apex and just received some code that should be > complete. I am at a loss as to how to re-build this stuff. > > I am going through the tutorial/man pages/rational support site but > the going is slow. > > Maybe someone here can help me quickly. > > I have a directory with 10 or so project.ss subdirectories. And then > for each of those directories there is one subdirectory with a build > number. In this subdirectory there are ada files. > > I am at a loss as to how to rebuild this stuff using the APEX IDE. > > If anyone can explain to me how this can be done, I'd truly appreciate > it. Likewise, if there is a simple tutorial on "reopening/rebuilding" > old source code, that'd be a blessing. You need to find the top level subprogram in the build. It will more than likely be a procedure without a separate specification, so look for a file that ends in .2.ada that doesn't have a corresponding .1.ada. If you open it and it appears to be a procedure body that with's a whole load of other stuff then you might have found it. Unfortunately it's not easy to locate it without knowing more about the project. Apex divides the project into SUBSYSTEMs (.ss directories) which are logically grouped packages, and to link an executable you need to have an appropriate VIEW of each subsystem. These are either WORKING (.wrk) views which can be modified, or RELEASE (.rel) views which can't (for instance, the predefined subsystems containing Ada.Text_IO, etc). Each view can import other views to give you your complete build. If the import set (the combined set of all the imports) is valid, you should be able to select the top level subprogram, and simply select 'Link...' from the 'Compile' menu which will give you a pop up dialog box. Just press OK and you should end up with an executable. This is obviously a very simplistic view, and there are stacks of things that could prevent it working, but if you need more info, let me know... Nige