Click above to get retro games delivered to your door ever month!

 Microsoft C / C++ / Quick C
------------------------------------------------------------------------------
 Blinker supports version 5.0 and later of Microsoft C / C++, and all
 versions of Microsoft Quick C for DOS real mode and Windows programs, and
 supports versions 5.1 and later of Microsoft C/C++ for protected mode
 programs. The following sample programs written in Microsoft C will be used
 throughout this section to illustrate the basics of linking Microsoft C and
 Quick C programs with Blinker.

 Overlaid programs must be compiled to use far calls, i.e. medium, large or
 huge memory model. Extended and dual mode programs must be compiled to use
 large or huge memory model.

 The Microsoft C/C++ graphics libraries for version 5.1 and later are fully
 supported in protected mode.

 For DOS extended programs written in Quick C use the BLXMSC51 library as the
 BLXMSCnn library.

 TEST.C
 void limerick (void);
 void main ()
 {
 limerick ();
 }
 LIMERICK.C
 <include <stdio.h>
 void limerick (void)
 {
    printf ("There was a young fellow from Microsoft\n");
 }

 The two modules are compiled as large model code as follows :
 Microsoft C

 CL -c -AL test.c
 CL -c -AL limerick.c

 Quick C

 QCL -c -AL test.c
 QCL -c -AL limerick.c

 DOS extended / non-overlaid program

 # TEST.LNK (This is a comment)
 # Comment out the next line for DOS real mode program
 BLINKER EXECUTABLE EXTENDED   # Create DOS extended program
 FILE test
 FILE limerick
 SEARCH BLXMSCnn               # Blinker dual mode library
 MIXCASE                       # Make link case sensitive

 This causes Blinker to link the two object modules specified in the FILE
 commands (test.obj and limerick.obj) to create a DOS extended program with
 the name TEST.EXE, which is the name of the first .OBJ file in a FILE
 command.

 Dual mode / overlaid program

 # TESTDUAL.LNK
 # Comment out the next line for dynamic overlays only
 BLINKER EXECUTABLE DUAL       # Create dual mode program
 BLINKER OVERLAY OPSIZE 50     # 50kb overlay area
 BLINKER OVERLAY PAGEFRAME ON  # Run overlays in pageframe
 BLINKER MESSAGE WINK          # Only wink one eye
 FILE test                     # This file is not overlaid
 BEGINAREA                     # Start of overlays
    FILE limerick              # This file is overlaid
 ENDAREA                       # End of overlays
 SEARCH BLXMSCnn               # Blinker dual mode library
 OUTPUT t                      # Output .EXE name
 MAP A,S                       # Create MAP file
 MIXCASE                       # Make link case sensitive

 16 bit Windows program

 # TESTWIN.LNK
 FILE test
 FILE limerick
 LIB llibcew, libw ...   # Windows libraries
 NODEFLIB                # No default libraries
 MIXCASE                 # Make link case sensitive
 DEFFILE TEST            # Use TEST.DEF
 # TEST.DEF
 NAME           TEST
 DESCRIPTION    'A small Windows program'
 EXETYPE        WINDOWS 3.1
 HEAPSIZE       1024
 STACKSIZE      8192

 Windows programs may require the Microsoft libraries to be explicitly
 specified in the link script file along with the NODEFLIB command.