Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!burl!codas!killer!richardh
From: richardh@killer.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: CodeView and Turbo C
Message-ID: <1612@killer.UUCP>
Date: Wed, 23-Sep-87 20:18:58 EDT
Article-I.D.: killer.1612
Posted: Wed Sep 23 20:18:58 1987
Date-Received: Sat, 26-Sep-87 10:02:50 EDT
References: <1485@killer.UUCP> <3320052@hpsrlc.HP.COM> <3826@watdcsu.waterloo.edu> <1909@ttrdc.UUCP>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 33
Summary: CodeView, Turbo C

In article <1909@ttrdc.UUCP>, kad@ttrdc.UUCP (Keith Drescher) writes:

> In article <1569@killer.UUCP> I write:
> >
> >And I'm looking forward to CODEVIEW as soon as I get it in my MASM 5.0 upgrade.
> >Then I'll use it with Turbo C.
> 
> How?
> 

Since I use TCC exclusively, I just added the -c and -y options to TURBOC.CFG
and then use Link, version 3.6, with the /co option. I still don't have 
symbolic access to non-external variables, but, as they say in Minnesota,
"Whatever." I do have access to multi-module line numbering information and
and all externally visible objects (functions and variables). 

Actually, it's not that automatic. I watched in horror as my 12k executable
grew to 18k+ when compiled and linked as per above. I tailor my compiler/
linker invocations to meet the current situation (as is recommended in the
CodeView docs, as well as by common sense.)


> program.   Maybe QuickC will be the answer to my needs.

Or maybe not. I quit searching for the holy grail a long time ago. Hence the
mixed strategy outlined above.

> -- 
> Keith Drescher (kad@ttrdc)          	   | ... You can check out any      

richard hargrove
...!ihnp4!killer!richardh
-------------------------