For any programmer or team struggling with builds and maintenance, this book can save dozens of errors and hours of effort. It shows you how to structure a large project and keep your files and builds under control over many releases and platforms. The building blocks are simple: common-sense strategies, public-domain tools that you can obtain on a variety of systems, and special utilities developed by the author.On two diskettes provided with the book, Jameson offers a complete system for managing directories, makefile templates, and source code revisions. Both free software and tools developed by the author are included.The tools and ideas offered here are efficient enough to be used by one person working on a PC, but powerful enough to support entire teams of developers. They've been tested in practice on projects from 50 to 100,000 lines of code. And complete, documented source code is included, in case you need to modify or extend the tools.In short, this book is an inexpensive, "one-stop-shopping" solution for code management problems. It can help you improve your personal software development process and can make it very easy for you to reuse and update shared code files.Topics covered in this book include:
Multi-platform directory structures for isolating and controlling platform dependent code.
Automatic makefile generating tools to promote uniform, portable makefiles on your projects and to save you time.
File sharing tools that make it easy to share the latest versions of files among multiple developers and software products, automatically. Since the sharing tools log all sharing operations, they can easily help you answer programming questions, such as, "Where did this file come from, and which programs will be affected if I modify it?"
RCSDO, a tool that performs version control operations on entire trees of files at a time. (RCS v5.5 is included, too.)
The source code provided runs on at least these 15 platforms: AIX, Amiga, Apollo Domain, Dell PC Unix (SVR4), HP-UX, Irix4, Linux, MS-DOS (Borland), MS-DOS (Microsoft), OS/2, NetBSD, NeXT, Solaris 1 (SunOS 413), Solaris 2, and Ultrix. The RCS v5.5 software has been specially modified for DOS-Unix network use and is known to run on MS-DOS (Borland), MS-DOS (Microsoft), and Solaris 1.0 (SunOS 413). The diskettes also contain precompiled binaries for MSDOS.Here is a sample of the tools included on the diskettes:
cmi: copy a shared file from its public location to the directory where it can be used for builds
cmx: copy a shared file from its source directory to a public location where other developers can get it
makenode: make a directory structure to hold a product's source files in the form that the other tools can work with
newmakes: generate makefiles throughout a product's directory structure
rcsdo: do common activities on a group of RCS files in bulk
twalker: generate a batch script that can traverse all files of a particular type in a directory tree
Our look is the result of reader comments, our own experimentation, and feedback from distribution channels. Distinctive covers complement our distinctive approach to technical topics, breathing personality and life into potentially dry subjects. Trapeze artists are featured on the cover of Multi-Platform Code Management. Acrobats appeared in art as early as 2500 B.C., when several were depicted in a painting on the wall of a tomb in the Nile Valley. The art of tightrope walking is thought to have originated in China, and Marco Polo described fantastic acrobatics displays, including "rope dancing," that he witnessed in the court of Kublai Khan. The Roman emperor Carinus is credited as being the first to sponsor a formal performance by acrobats, in the third century.The trapeze entered the modern age in 1859, thanks to two French trapeze artists. On June 30, 1859, Emile Gravelet, who called himself Blondin, crossed Niagara Falls on a tightrope for the first time. He repeated this feat numerous times throughout the summer of 1859, drawing huge crowds each time. News of these crossings created such a sensation that high-wire acts came into great demand throughout the world.That same year another young Frenchman named Jules Leotard, assisted by his father, developed a routine in which he "flew" from one device to another. He is believed to be the first flying trapeze artist. He not only created a sensation that would forever become a staple of circus acts, he also gave his name to the costume acrobats and dancers continue to wear to this day.Danger has always been an integral part of the appeal of the trapeze, with sometimes tragic results. Some of the most legendary trapeze artists to die while performing their art are Lillian Leitzel, in 1931, and several members of the Flying Wallenda family, including Willy Wallenda, in 1933. ...Edie Freedman designed this cover using a nineteenth-century engraving from the Dover Pictorial Archive. The cover layout was produced with QuarkXPress 3.3 using the ITC Garamond font. Edie also designed the interior layout.Text was prepared in SGML using the DocBook 2.1 DTD. The print version of this book was created by translating the SGML source into a set of gtroff macros using a filter developed in-house by Norman Walsh. Steve Talbott designed and wrote the underlying macro set on the basis of the GNU gtroff -gs macros; Lenny Muellner adapted them to SGML and implemented the book design. The GNU groff text formatter version 1.08 was used to generate PostScript output.The figures were created in Aldus Freehand 4.0 by Chris Reilley and Karla Tolbert. The colophon was written by Clairemarie Fisher O'Leary with help from Michael Kalantarian.