•  Back 
  •  Pure C Help 
  •  Index 
  •  Tree View 
  •  Cross references 
  •  Help 
  •  Show info about hypertext 
  •  View a new file 
Topic       : Pure C Documentation
Author      : John Kormylo
Version     : PC.HYP 1.1
Subject     : Documentation/Pure C
Nodes       : 193
Index Size  : 5414
HCP-Version : 3
Compiled on : Atari
@charset    : atarist
@lang       : en
@default    : 
@help       : Help
@options    : +g -i -s +x +z -t4
@width      : 75
View Ref-File[ Project File ]

The project file is used by the Project commands to define which files
need to be compiled, assembled and/or linked together to create an
executable program.

Since even the most simple programs require a certain amount of
linking, a project file is always needed to run a program.  The
provided file DEFAULT.PRJ will run a program if its source code is
entirely contained in the active edit window.

Project files have the following syntax:

  { <output_file> | * }
  { .L [ Linker Options ] }
  { .C [ Compiler Options ] }
  { .S [ Assembler Options ] }
  <module_name1> { [ <options> ] }  { ( <include_files> ) }
  <module_name2> { [ <options> ] }  { ( <include_files> ) }

The <output_file> should have either a .TOS .TTP .PRG .ACC or .LIB
extension. See Program Extensions.

Each <module_name> can either be an asterisk '*', to represent the
active edit window, a source code filename, an object filename, a
library filename, or an included project filename.  These modules will
be linked in the order they appear, so the startup module PCSTART.O
PCXSTART.O or PCVSTART.O must go first and the Libraries usually
go last.

The <options> list refers to Compiler Options or Assembler Options,
and only applies to source code files.  (These lists can be used to
set flags which are clear by default, but not to clear flags which
are set by default.)

The <include_files> list forces the module to be re-compiled if any
of the listed files is changed.

See also Project Examples and Linker.