Laserfiche WebLink
imake <br />system to system. The program therefore allows software to be distributed on different <br />platforms using a single set of distribution files. A good reference for the imake program is Software <br />Portability with , by O'Reilly & Associates, Inc. <br />imake <br />imake make make <br />The program is built on top of the program and contains features that does not. <br />make <br />The program is ideal for compiling a single program (and is relatively simple to use); <br />however, its features are limited when maintaining a large software system, and it is difficult to <br />make <br />guarantee that makefiles will work on different platforms. In particular, is difficult to use <br />imake <br />when software for a product is spread among different directories. The program helps to <br />guarantee that imakefiles and associated makefiles will work on different systems, but the use of <br />imake make imake <br /> requires more configuration effort than , and a greater effort to learn <br />imake <br />configuration file rules. Consequently, it is suggested that the command initially be used only <br />make <br />when dealing with X Window System software, or in places where the limitations of the <br />command can be overcome. <br />make imake <br />RTi suggests that specific guidelines for using and be developed early in Phase II, after <br />the source code structure for existing programs (e.g., MODSIM) is reviewed. Existing programs <br />may have (i)makefiles that are sufficient for the purposes of the project. RTi has extensive <br />make <br />experience in using make and has guidelines for using at RTi, and will use this experience in <br />developing the (i)makefiles for the CRDSS. The file structure for the CRDSS described in Task <br />Memorandum 1.05-23 indicates how files are to be organized. This organization will define the <br />basic contents of configuration files used to manage software. <br />RTi will be responsible for developing a (i)makefiles that reflect the structure of the CRDSS system. <br />Template files will be distributed to the development team so that (i)makefile guidelines will be <br />followed. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />make imake <br />The following recommendations are made regarding the use of the and programs for <br />the CRDSS development work: <br />make <br />The program manages software products by updating target products based on the <br />? <br />modification dates of dependency files. It has many features for managing software but <br />lacks provisions for managing products that span multiple directories. <br />imake <br />The program is used in conjunction with portable configuration files for software <br />? <br />products and allows software to be easily distributed. The program uses the configuration <br />make <br />files to create a machine-dependent makefile that can be used by the command. The <br />imake <br />use of adds another layer of complexity to software management because of the <br />imake <br />extended configuration files; however, the benefits of using can be important where <br />make <br /> cannot perform satisfactorily. <br />make <br />Software maintenance in the CRDSS will initially use the command with template <br />? <br />imake <br />makefiles supplied by RTi. The program and configuration files will be used where <br />make <br /> cannot perform satisfactorily and where X Window System software is used. The <br />imake <br />use of will be extended in the future as the complexity of the CRDSS increases. <br />2 <br />A275 05.10.94 1.05-21 Malers <br />