PRODUCT  :  Borland C++                           NUMBER  :  1332
  VERSION  :  3.x
       OS  :  DOS
     DATE  :  October 25, 1993                         PAGE  :  1/2

    TITLE  :  Creating stand alone Assembler programs in the IDE.





       This document details how to build and run a pure assembler
  program from inside the Borland C++ v3.0 or 3.1 IDE.

       The Borland C++ IDE is currently designed to build C or C++
  programs and libraries.  Assembler modules of C/C++ programs are
  supported, but the basic assumption is that the program is a
  C/C++ program and as such needs internal support such as the C
  startup code and the C runtime libraries when linking.  When
  building an assembler program, these extra items are not only
  unnecessary, but actually harmful, so they need to be removed
  somehow.  This document describes the steps required to build and
  run a standalone assembler program from the IDE.

       - The C compiler wants to link in the startup code.  This is
       clearly not desired for an assembly program and the only way
       to disable this is to have an assembly file titled C0.ASM
       (or start with C0xxx.asm).  If a project file is being used,
       this must be the first module listed in that file.  Thus if
       there is only one .ASM module in the program, it will be
       called C0xxx.ASM.  If there is more than one, the first one
       in the list in the project file will be called C0xxx.ASM.

       - All libraries should be disabled.  Go to Options | Linker
       | Libraries, uncheck Turbo Vision and Graphics, and make
       sure that OWL, Container Class, and Runtime Library are all
       set to <None>.

       - The IDE has difficulties dealing with assembler programs
       that have debug information.  So set Options | Debugger to
       Standalone.  This way the IDE can run the program, and if
       debuging is necessary, you can transfer to the Turbo
       Debugger from the <Alt-Space> menu.
       NOTE: It is usually not very helpful to use the integrated
       debugger on an assembler program anyway

       - One last note,  If there is no project file, the only way
       to assemble the code is to run Turbo Assembler from the
       transfer menu.  Doing Options | Compile | Compile will
       invoke the C compiler on the file which is bad news.  If
       there is a project file, this is not an issue, as the
       project manager automatically calls Turbo Assembler on
       .ASM files.













  PRODUCT  :  Borland C++                           NUMBER  :  1332
  VERSION  :  3.x
       OS  :  DOS
     DATE  :  October 25, 1993                         PAGE  :  2/2

    TITLE  :  Creating stand alone Assembler programs in the IDE.




       For example, suppose we have an assembler program that
  consists of the following modules:
            ONE.ASM   TWO.ASM   THREE.ASM   FOUR.ASM

       To build this in the IDE, rename ONE.ASM to C0ONE.ASM and
  then insert all four modules into the project file, making sure
  that C0ONE.ASM (formerly ONE.ASM) is the first file.  Then select
  Options | Linker | Libraries, uncheck Turbo Vision and Graphics,
  and set Object Windows, Container Class, and Runtime Libraries to
  <None>.  Finally, set Options | Debugger to <Standalone> and save
  the project.  It is now ready to go and doing a <Build All> for
  example, should build the program.


  DISCLAIMER: You have the right to use this technical information
  subject to the terms of the No-Nonsense License Statement that
  you received with the Borland product to which this information
  pertains.