Path: utzoo!utgpu!attcan!uunet!ncrlnk!ncrcae!ncr-sd!hp-sdd!hplabs!hp-pcd!hplsla!bam
From: bam@hplsla.HP.COM (Ben Mejia)
Newsgroups: comp.lang.c++
Subject: Re: Managing C++ Libraries: Dependencies and Headers
Message-ID: <6590070@hplsla.HP.COM>
Date: 9 Nov 88 23:14:07 GMT
References: <5078@thorin.cs.unc.edu>
Organization: HP Lake Stevens, WA
Lines: 15


    I use the scheme Walter Bright recommends and it works very well.
This covers a lot of bases.  The next thing to worry about is how
to write a Makefile for a program.

    I use the nmake program (from the ATT toolchest), which automatically
examines the #include's to build its own dependency graph.  So when
one changes a particluar header file, all the dependents get updated.
I highly recommend nmake.  Most Makefiles collapse to:

program  :: <source file list>

--
    bam                                       bam%hplsla@hplabs.hp.com
                                              (206) 335-2203