Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| MicroSoft C 6.0F nicholso@pioneer.arc.nasa.gov (1990-07-07) |
| Re: MicroSoft C 6.0F acook@athena.mit.edu (1990-07-14) |
| Re: MicroSoft C 6.0F nicholso@pioneer.arc.nasa.gov (1990-07-16) |
| Re: MicroSoft C 6.0F dave@thundercat.com (1990-07-18) |
| Re: MicroSoft C 6.0F 6600sirt@ucsbuxa.ucsb.edu (1990-07-19) |
| Re: MicroSoft C 6.0F bnrgate!bwdls58.bnr.ca!mlord@uunet.UU.NET (1990-07-24) |
| Newsgroups: | comp.compilers,comp.os.msdos.programmer |
| From: | bnrgate!bwdls58.bnr.ca!mlord@uunet.UU.NET (Mark Lord) |
| Keywords: | graphics |
| Organization: | Bell-Northern Research, Ottawa, Canada |
| References: | <325@tygra.ddmi.com> <1990Jul19.182239.6948@esegue.segue.boston.ma.us> |
| Followup-to: | comp.os.msdos.programmer |
| Distribution: | na |
| Date: | Tue, 24 Jul 90 23:44:08 GMT |
In article <1990Jul19.182239.6948@esegue.segue.boston.ma.us> 6600sirt@ucsbuxa.ucsb.edu (Mike O'Brien) writes:
>
>The big difference, though, is that MSC does not use the equivalent of
>BGI files. All of the graphics support (exept fonts) is linked into
>the EXE. On the plus side, that means you don't have to distribute
>BGI files with everything you write. On the down side, it means that
>you can't modify MSC's functions to work with Super VGA or anything.
Actually, .BGI files can also be linked into the .EXE by using a turbo
utility to first convert the ones you want to use into .OBJ format,
and then simply linking them in. Check out the Turbo-C docs for details.
--
___Mark S. Lord__________________
| ..uunet!bnrgate!bmerh614!mlord |
| ..uunet!bnrgate!mlord%bmerh614 |
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.