Managing Projects with make (A Nutshell Handbook)

Andrew Oram

ISBN 10: 0937175900 / ISBN 13: 9780937175903

Published by O'Reilly & Associates, 1993

About this Item

Ausreichend/Acceptable: Exemplar mit vollständigem Text und sämtlichen Abbildungen oder Karten. Schmutztitel oder Vorsatz können fehlen. Einband bzw. Schutzumschlag weisen unter Umständen starke Gebrauchsspuren auf. / Describes a book or dust jacket that has the complete text pages (including those with maps or plates) but may lack endpapers, half-title, etc. (which must be noted). Binding, dust jacket (if any), etc may also be worn.

Seller Inventory # M00937175900-B

Bibliographic Details

• Title: Managing Projects with make (A Nutshell Handbook)
• Publisher: O'Reilly & Associates
• Publication Date: 1993
• Language: English
• ISBN 10: 0937175900
• ISBN 13: 9780937175903
• Binding: Soft cover
• Edition: 2nd Edition
• Condition: acceptable

About this title

Synopsis

make is one of UNIX's greatest contributions to software development, and this book is the clearest description of make ever written. Even the smallest software project typically involves a number of files that depend upon each other in various ways. If you modify one or more source files, you must relink the program after recompiling some, but not necessarily all, of the sources.

make greatly simplifies this process. By recording the relationships between sets of files, make can automatically perform all the necessary updating.

For large projects with teams of programmers and multiple releases, make becomes even more critical. But in order to avoid spending a major portion of your maintenance budget on maintaining the Makefiles, you need a system for handling directories, dependencies, and macro definitions. This book describes all the basic features of make and provides guidelines on meeting the needs of large, modern projects.

Some of the issues addressed in the second edition include:

• Projects covering several directories.
• Maintaining consistency when building variants of a program.
• Automatic generation of header file dependencies.
• Forced rebuilds of existing files.
• A description of free products that contain major enhancements to make.
• Listings of the features that vary between different versions of make and simple ways to test them.
• More detail and examples on common errors, use of the shell in make, formal rules of syntax in make, and support for various utilities.

About the Author

With a background in journalism and farming, Steve Talbott has worked for the past 12 years in technical documentation. Prior to joining O'Reilly & Associates he managed the Technical Publications Group at Concurrent Computer Corporation, and before that was responsible for the development of computer-based documentation tools at Concurrent. In his editorial position at O'Reilly, Steve develops new titles across the company's product line. He has focused on 3D graphics and software standards. Avocationally, Steve pursues an interest in the broader social and cultural implications of computers. Over an eight-year career in computer documentation Andrew Oram has evolved from a proponent of the congenial user-oriented approach to a fanatic on the subject of explaining models and internal operations so as to empower computer users. He was not prepared by his education (which included music and social work) for the philosophical and pedagogical demands of this role, but seems to have fallen into it. His technical writing career encompasses Honeywell Information Systems (now Bull), CSPI (still itself, incredibly), MASSCOMP (now Concurrent Computer Corporation), and currently O'Reilly & Associates, where he is an author. He also once worked as a college instructor teaching PDP-11 assembly language. Topics of his manuals include network administration and programming, array processors, languages, debuggers, and real-time programming---in fact, writing about shell commands in Managing Projects with make has proved to be a relaxing break. His recent research focuses on making user documentation verifiable through the same quality-assurance process used on other components of a computer system. Whenever he gets a free moment away from his three-year-old, seven-year-old, and other commitments, he works with Quality Assurance teams on this project and publicizes it through articles and conferences.