home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!mucs!iwp
- From: iwp@cs.man.ac.uk (Iain Phillips)
- Newsgroups: comp.sys.transputer
- Subject: Re: occam
- Summary: Use imakef for makefiles
- Message-ID: <5715@m1.cs.man.ac.uk>
- Date: 12 Aug 92 12:53:15 GMT
- References: <2490@news.cerf.net> <JAN.92Aug12103429@pallas.neuroinformatik.ruhr-uni-bochum.de>
- Sender: news@cs.man.ac.uk
- Reply-To: iwp@cs.man.ac.uk (Iain Phillips)
- Organization: Department of Computer Science, University of Manchester UK
- Lines: 17
-
- In article <JAN.92Aug12103429@pallas.neuroinformatik.ruhr-uni-bochum.de> jan@pallas.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) writes:
- > ... a collegue
- >spent several days of labour (as in GULAG) to produce the makefile. And every
- >time you add a file to the thing, you start thinking about the dependencies
- >and what you have to add to the makefile. None of that with the TDS. ...
-
- The imakef tool supplied by Inmos with the toolsets does an excelent job in
- producing makefiles. It handles all the dependancies. If your program has
- only one executable and providing you have your #USEs, #INCLUDEs and ISEARCH
- variable correct then there's nothing to worry about. Here at Manchester,
- converting a TDS program to toolset has just been a case of using iflat,
- renaming one file, a couple of edits, imakef and make. The recent versions
- of imakef even add rules for deletion of intermediate files to save disk
- space, and no dependancy checking of ISEARCH files for faster making.
- --
- Iain Phillips iwp@cs.man.ac.uk or iwp@uk.ac.man.cs
- Dept of Computer Science, University of Manchester, M13 9PL. U.K.
-