Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!lll-lcc!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.misc
Subject: Re: Obnoxious software (was Re: C license agreements)
Message-ID: <462@sugar.UUCP>
Date: Mon, 3-Aug-87 08:40:56 EDT
Article-I.D.: sugar.462
Posted: Mon Aug  3 08:40:56 1987
Date-Received: Fri, 7-Aug-87 04:30:06 EDT
References: <8387@brl-adm.ARPA> <6146@brl-smoke.ARPA> <870@bsu-cs.UUCP> <24@splut.UUCP>
Organization: Sugar Land UNIX - Houston, TX
Lines: 24
Summary: That's what 'make' is for, Jay. Also, try 'cc -v'.

In article <24@splut.UUCP>, jay@splut.UUCP (Jay Maynard) writes:
> If I'm doing a 'cc foo*.c -o foo', there's no way to tell short of switching
> consoles (easy under Microport) and running ps. Bleh. I'd like a way to know
> how far along things are going so I can test my program.

You haven't achieved guru-nature yet, grasshopper.

Instead of doing 'cc foo*.c -o foo', try making a makefile:

# Makefile for foo:
OBJS= foo.o foo1.o foo2.o foo3.o

foo: $(OBJS)
	cc $(OBJS) -o foo

This way you can also not recompile already compiled programs. Believe
it or not, but there are actualy filters that work on the output of cc.
One that I know of generates an annotated listing, another just plain
inserts the error messages as comments in your source. You don't want to
prevent such things, do you? Also, there are a couple of cases I know of
where cc is actually run in shell scripts. I guess you don't mind having
weird copyright messages showing up in the middle of a menu somewhere.
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter (I said, NO PHOTOS!)