6.4: GNO with ORCA: Where should my C header files go?
Description
This article is from the Apple II GNO FAQ, by Devin Reade with numerous contributions by others.
6.4: GNO with ORCA: Where should my C header files go?
A#6.4: === See the CAVEAT in Q#6.1 ===
While it is possible to have all of your header files in one
directory hierarchy (this is how it was done in the stock v2.0.4
distribution), it is STRONGLY advised that you keep separate
directory hierarchies. They are:
/usr/include
/HFSinclude
/lang/orca/libraries/orcacdefs
/lib/orcacdefs
/usr/local/include
The /usr/include directory should contain all the header files
that ship with GNO. This will include some subdirectories like
sys, machine, and net.
In GNO v2.0.6 there are a few files that don't conform to ProDOS
naming conventions. These files should be placed in the /HFSinclude
hierarchy.
ORCA/C comes with its own set of header files. Some of these
are used by GNO while others are ignored (because header files
of the same names exist in one of the other directory hierarchies).
All of these header files should be left in the
/lang/orca/libraries/orcacdefs directory (see Q#6.2).
/lib/orcacdefs corresponds to 13/orcacdefs under GNO. It should
contain only one file, defaults.h. See Q#6.5.
/usr/local/include, like everything else in the /usr/local hierarchy,
is not used by the GNO base install. This hierarchy is reserved
for site-specific packages that you decide to add. In particular,
/usr/local/include should be used for any header files that you
decide to add to your system, and which are not part of the
base installation.
Continue to:
My Books
