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

  
  Compile your application using CLIPPER.EXE as normal.  You
  probably need to #include "WINDOWS.CH" to define the many
  values applicable in the Windows environment.  There are other
  files in the INCLUDE directory that are useful, such as
  FONT.CH.
  
  To link your application with Clip-4-Win make sure your linker
  will look for RDD's, then the CLIP4WIN.LIB library, and
  finally the Clipper libraries.
  
  If using Microsoft's linker, you can use the definition file
  CLIP4WIN.DEF (or a definition file based on it), so that a
  Windows-style executable is produced.  You will need the  /SE
  (/SEGMENTS)  option, and you may need the  /NOE
  (/NOEXTDICTIONARY)  option.
  
  You can use the /ALIGN:16 option to reduce the size of your EXE file.
  
  Example
  
     clipper myapp /w
  
     link /se:600 /al:16 myapp, , , myrdd+clip4win, clip4win.def;

  To link the Clipper debugger, CLD.LIB, add C4WDBG.LIB to your
  OBJ files and CLD.LIB to your LIB files:
  
   link /se:600 /al:16 myapp+c4wdbg.lib, , , myrdd+clip4win+cld, clip4win.def;
  
  If you are using a Microsoft linker prior to LINK 5.30 you may
  need to remove the "3.1" from the line
            exetype  windows  3.1
  in the .DEF files.
  
  The CLIP4WIN.DEF file specifies the Windows "stub" file
  C4WSTUB.EXE, which is just a tiny program that runs under DOS
  to tell you that you should be using Microsoft Windows.  It is
  equivalent to the WINSTUB.EXE program you may be familiar with
  (from the Windows SDK).  If you wish, you can use that program
  or any other suitable .EXE program instead of C4WSTUB.EXE.
  
  When linking a Windows program do not use overlays; there is
  simply no need, as Windows manages memory automatically.
  
  Note
  If you are using a Microsoft linker prior to LINK 5.30 you may
  find that everything appears to work, but that Windows issues
  an Application Compatibility Warning every time you start your
  application.  The EXEMARK program included with Clip-4-Win can
  be used to mark your application as suitable for Windows 3.1
  as follows:
            exemark   app.exe   3.1
  However, this is not recommended.  If you experience problems
  with your application as a result of this process you should
  make sure that they are not a result of using an out-of-date
  linker.
  
  
  Much faster than MS LINK is Blinker 3 (from Blink Inc.).  A
  sample link script is in the blinker\ directory.
  
  Example
  
     blinker file myapp lib myrdd,clip4win deffile clip4win.def
  
  To link the Clipper debugger, CLD.LIB, add C4WDBG.LIB to your
  OBJ files and CLD.LIB to your LIB files:
  
     blinker file myapp,c4wdbg.lib lib myrdd,clip4win,cld deffile clip4win.def
  
  
  OptLink (from SLR Systems Inc.) can also be used.  It has two
  particularly useful features: compression (your EXE will be
  about half its size otherwise), and it can build in resource
  files, saving you some time.
  
  Example
  
     link /winpack /al:16 myapp, , , myrdd+clip4win, clip4win.def;
  
  To link the Clipper debugger, CLD.LIB, add C4WDBG.LIB to your
  OBJ files and CLD.LIB to your LIB files:
  
  link /winpack /al:16 myapp+c4wdbg.lib, , , myrdd+clip4win+cld, clip4win.def;