Club Amiga de Montreal - CAM/CAM_CD_1.iso/files/240.lha/IntegratedCCompilerEnv/ICCE.DOC

Text File | 1989-05-08 | 5.1 KB | 112 lines

                ICCE 1.4

                     BY C&P Software


        (* NOTE: Version 1.4 is only an optimization version the
    code has been shortened from 14XXX bytes to 13039 bytes.  It should
    be a little faster. *)

        Yes, for too long now the 'C' programmers on the AMIGA
    have gone without the luxury of a Integrated C Compiler Environ-
    ment.  Well here is ICCE,  I know that it isn't exactly the
    cadillac of environments but it will avoid the agony of typing
    all the commands you need to type all the time when you are in
    the development phase of that critical game/utility or whatever
    it is you program.  I sincerely hope that you will enjoy this
    small utility and that it will accelerate your program develop-
    ment.

         Here are the explanations of those criptic key strokes:

    KEY    EXPLANATION
    ---    -----------

    'D'    Select the working drive for the program.
    'T'    Select the type of Command line interface ICCE will
        open when you select the 'G' command. 'cli' is a regular
        old CLI.  Shell is the NewShell that comes with the 1.3
        Workbench Upgrade.
    'P'    Select the working path for the program.
    'W'    Select the name of the working file.
        ***********************************************************
        *     If perhaps sometimes your drive, path or Workfile   *
        *  selections don't appear to work, It's probably because *
        *  ICCE checks for the validity of the path that you give *                                                       *
        *  it and also appends a '.c' to the end of the workfile  *
        *  if one was not supplied.                               *
        ***********************************************************
    'O'    Select the compiler and linker options + the linker's
        libraries.  When nothing is entered, ICCE assumes that you
        want to keep the previously selected options.  To input no
        options at all, when the cursor is on the line desired,
        enter a blank.
        ***********************************************************
        *     Compiler, Assembler and linker options or libraries *
        *  are not checked for validity like the drive, path and  *
        *  filename therefore watch what you put in there.  But   *
        *  anyway the worst that can happen is that the compiler, *
        *  assembler and/or linker will complain because they do  *
        *  not recognized the options passed to them.  *** NOTE:  *
        *  if the Compiler, Assembler and/or Linker detect a      *
        *  FATAL ERROR, they output goes to 'stderr' which I      *
        *  cannot redirect as of yet!!! (HELP!!!)                 *
        ***********************************************************
    'A'    Specify the arguments you would like passed to the final
        compiled product when you 'R'un it.
    'E'    Edit your file, ICCE will call the editor called 'ed' in your
        current C: directory.
    'C'    Calls the Manx Aztec 'C' compiler with the specified
        options and your working file, also calls the Assembler with
        the specified Assembler options plus your file.ASM.
    'L'    Calls the Manx Linker with the specified options, the
        working file and the specified libraries.
    'R'    Runs your programs as a separate task.
    'G'    Provides you with a CLI as a means of entering those
        DOS commands that ICCE cannot perform for you such as
        'copy', 'delete', etc,...
    'F'    View the directory that you have selected with the 'D'
        and 'P' commands.
    'M'    Calls the MAKE utility supplied on the Aztec 'C' release
        disks.  MAKE must reside in your compiler path and there
        must be a 'makefile' present in the Work directory.
    'S'    Manx Source Level Debugger command. Selecting this command
        will force a recompile and link with the appropriate
        debugger options included so that ICCE can subsequently
        call SDB for you. (NOTE: SDB must be in your compiler path.)
    'Q'    Quit ICCE.

        When ICCE is first entered, it will look for the file
    'ICCE.cfg' to be in your S: directory, if the file is not found,
    ICCE will go ahead and use it's defaults for the compiler and
    linker options as well as it's default library.  If it doesn't find
    the compiler in the SYS: directory, it will go ahead and ask you for
    a path which MUST include the '/' at the end:
        i.e.: "Compiler Path: DH0:manx/"
    would be a valid entry, but: "DH0:manx" would not.
    ***** NOTE: This was necessary since ICCE is now a child process of
    the CLI/SHELL it was started from and has no idea about the path
    that you have set for that CLI/SHELL.  If someone knows how to pass
    that path to the child process I would appreciate the code to do
    it and would incorporate it as soon as possible with the necessary
    credit given to the provider.  THANX in advance. *****

        Upon exit, it will save all of the options that you have
    chosen in the 's:ICCE.cfg' file    so that the next time you bring
    ICCE up it can restore the environment that you had set.

        Well there they are I hope that these compact explanations
    are enough to get you going.  Happy Compiling...

                        PAUL FORTIN

    P.S.: You can reach us(C&P Software) on CAUG and BBS-JC as PAUL
          FORTIN and PLINK as TONY*S.

    P.S.S.: Do not forget to do the 'sets' that the compiler will
        need and to add the directory where your compiler and
        the source level debugger reside in your path (*** with
        the DOS 'path' command ***)