| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 660.1 | try to live with that ... | KBOMFG::COLDITZ | Peter Colditz @KBO | Tue Jan 12 1988 08:49 | 7 |
| If you link with $ link/map you can have a look to all linked modules
out of the VAXCRTL.OLB into the image. The minimum size of a C image
is 87 blocks.
Try to access the C notes file TLE::VAXC for much more inputs.
Peter
|
| 660.2 | A tumour on the side of the C | MDVAX3::COAR | M��se Choreographer | Tue Jan 12 1988 09:59 | 7 |
| Yah, VAX-C includes a bunch of object modules into the .EXE, rather
than just a reference to a shareable library, because (as I recall)
of the rather bizarre way VAX-C handles some of its `standard
variable.' The PSECT attributes don't permit inclusion in a shareable
library, or something like that.
#ken :-)}
|
| 660.3 | Use A Higher Version? | FOO::BHAVNANI | When in doubt, blame the compiler. | Tue Jan 12 1988 12:01 | 13 |
| What version of VAXC are you using? On versions >= 2.1, I do
$ cc foo
$ link foo, tt /opt
sys$share:vaxcrtl.exe/sh
^Z
$ r foo
and get reasonable size .EXEs. I used to have the same problem
as you with VAXC 1.0. I suggest you upgrade to 2.3. Lots of nice
library routines, including Curses.
/ravi
|
| 660.4 | .3 works | 38007::ZARLENGA | Rowdy Roddy Piper personified | Thu Jan 14 1988 18:39 | 6 |
| You can get .EXEs as small as 4 blocks by using the method
demonstrated in .3.
I do it all the time.
-mike z
|