Article View: comp.windows.ms.programmer
Article #1784Re: Link problem using CodeView
From: Mark Boyd
Date: Thu, 21 Mar 1991 15:09
Date: Thu, 21 Mar 1991 15:09
17 lines
1234 bytes
1234 bytes
> table. Ugh. One current (possible) solution is to get another linker that
> understands the CodeView syntax and runs in extended memory. It would be
> nice, though, if we could use the Microsoft linker. The link parameters we
> are using are:
We did just that. We found the OPTLINKS linker (made by SLR Systems) that is
much better than the Microsoft linker. It will link files for DOS, Windows
2.10, Windows 3.0, and OS/2. Here are some of the benchmarks:
Microsoft linker OPLINKS linker Size
---------------- -------------- ----
.EXE w/o CVW 00:01:06 00:00:30 720K
.EXE with CVW 00:02:12 00:00:36 1500K
Mark Boyd
Inter-Tel, Inc.
Technical Details
Message-ID:
<353@intertel.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!intertel!boyd_mReferences:
<1991Mar15.022704.24298@oracle.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!intertel!boyd_m From: boyd_m@intertel.UUCP (Mark Boyd) Newsgroups: comp.windows.ms.programmer Subject: Re: Link problem using CodeView Summary: A different linker Message-ID: <353@intertel.UUCP> Date: 21 Mar 91 15:09:58 GMT References: <1991Mar15.022704.24298@oracle.com> Organization: Inter-Tel, Inc., Chandler, AZ Lines: 16