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

  ONERROR= <compiler> <editor> <editor directive>

    PBMake now includes a compiler error trap which makes your editor
    jump directly to the line in your code which created the error.

    Of course, you will have to use an editor that supports this, like
    Qedit or MultiEdit. ( and many others )

    PBMake also loads the error list at the same time as the source
    module with the error. Now, you can work all of the errors found in
    that source module in one pass by flipping back and forth between
    the source and the error list.

    You can set PBMake up to compile multiple languages and jump on
    error to a different editor for each language.

    PBErrLine is used to parse the captured output from the compiler and
    then create a batch file which calls your editor to edit the correct
    source code at the line number where the error occurred.

    PBErrLine can correctly identify errors from Clipper, Microsoft C,
    Turbo Assembler and Microsoft Assembler.


  PBInit now creates a small batch file named MK.BAT. MK.BAT is simply a
  shortcut file that eliminates you needing to type MAKE FILENAME, since
  that is what it contains. I guess I'm just lazy.

    So, assuming that you limit yourself to one executable per
    directory, you can compile by typing:

    MK <Enter>


  PBMake now has a CLEANUP= directive which will delete junk and temp
  files out of your working directory.


  More fine tuning for speed. Chopped out a bunch of redundant code.


  Updated this .NG file extensively.


  Added the DOS command line /LINK flag, which will cause the linker to
  run even if the make engine does not think it needs to.


  New Features for PBInit!

  Rather than it's original intent of creating a blank template for you
  to start from, which it can still do, PBInit is now capable of
  creating .MAK scripts directly from your link script. In fact, PBInit
  has received a complete overhaul. PBInit can create a far more
  comprehensive .MAK script that you would generally create for
  yourself, including complete references to any .LIB file, all .CH
  files used in your source code and the correct FLAG= lines for each
  source code module.

  PBInit now uses a small .INI file in the same directory as the
  executable to set up the default compiler, editor and editor flag for
  the jump to error feature. You do not need to have this file in your
  working directory.


  PBMake now preprocesses your .LNK script with the same directives
  that were passed in to the .MAK script.

  This means that you can now use #IFDEF, #IFNDEF, #ELSE, #ENDIF,
  #DEFINE and #UNDEF in your link scripts and they will be obeyed based
  on the same rules that apply to PBMake .MAK scripts.

  This will now work correctly in your link scripts:

  #ifdef DEBUG
     file CLD.LIB
  #endif

  Since PBMake now preprocesses your link script, it uses the processed
  link script to link with instead of the real link script. If you want
  to see the processed link script which is normally cleaned up after
  immediately, simply place a /P on the make request line. The processed
  link file will have the same name as the original link script with a
  .PPL extension. (MYLINK.LNK becomes MYLINK.PPL)

  PBInit now has the ability to refresh the paths on your INCLUDE= and
  LIB= files in the .MAK script. This is useful if you take your make
  files back and forth to two machines that are not set up identically.