<small> </small><big> </big><small> </small>
<ol>
<small> </small><big> </big><small> </small>
+
+<big>DEPRECATED</big>
<li><big> **REVISE** out of date... This variable has been needed
since clam became
- part of the YETIcode project (at <a href="http://yeticode.org/">http://yeticode.org</a>).</big></li>
+ part of the YETIcode project (at <a href="http://feistymeow.org/">http://feistymeow.org</a>).</big></li>
<small> </small>
<li><big>The default location for clam is under the FEISTY_MEOW_SCRIPTS directory in a
folder named clam.<br>
<small> </small><big> </big><small> </small>
<ol>
<small> </small><big> </big><small> </small>
- <li><big>The hoople/bin directory in the archive has
+ <li><big>The CLAM_BINARIES directory in the archive has
pre-built
versions of tools used by clam during a build.<br>
</big></li>
<small> </small><big> </big><small> </small>
<li><big>The standard source code repository is a directory
called
- "hoople"
- in the user's home directory. If you decompress the hoople
+ "feisty_meow"
+ in the user's home directory. If you decompress the feisty_meow
library archive in your home directory, you should be all set to
perform a build.</big></li>
<small> </small><big> </big><small> </small>
- <li><big>See the HOOPLE website for more details about
+ <li><big>See the Feisty Meow Concerns Ltdwebsite for more details about
downloading that codebase (<a href="http://feistymeow.org">http://feistymeow.org</a>).<br>
</big></li>
<small> </small><big> </big><small> </small>
<h3><big><a name="TUT_IMPORTANT_VARS"></a>Important Variables</big></h3>
<big>
The clam root directory is pointed to by an internal variable called
- "CLAM_DIR",
+ "CLAM_SCRIPTS",
defined in $/variables.def. This variable is used by the clam
system
to find extra files that might be needed by derived makefile
support.
It is important to change this to the appropriate value when you are
- using the system in a different location. The CLAM_DIR variable
+ using the system in a different location. The CLAM_SCRIPTS variable
can either
be directly edited in $/variables.def, or it can be overridden in the
environment
are
generated. All files generated by compilation are stored in the
repository
- directory (by default, either "~/hoople" in Linux or "l:\" in
+ directory (by default, either "~/feisty_meow" in Linux or "l:\" in
win32). There are three TYPEs supported so far: </big></p>
<ul>
<small> </small><big> </big><small> </small>
programs.</big></li>
<small> </small><small></small>
</ul>
- <big> Projects of the "library" type will
+
+<big>DEPRECATED</big>
+ <big>
+
+ Projects of the "library" type will
be given
an include directory named after the project, such as
- "~/hoople/include/basis".
+
+ "~/feisty_meow/include/basis".
The include directory is created as a copy of the headers in the
project's
directory . Library projects will also have their final products
Projects that are of type "application" will
have their executables
copied to the executable directory in the repository (such as
- "~/hoople/exe").<br>
+ "~/hoople/exe").
+
+<br>
The "test" type of project
will be promoted to a subdirectory named after the PROJECT that resides
under the test hierarchy in the repository (such as
"~/hoople/tests/turbodog").
</big>
+
+<big>DEPRECATED</big>
<p><big> SOURCE is a list of files that
are to be
compiled
<blockquote><big>MIDL is also a provided macro; it executes the
Microsoft
IDL compiler. </big></blockquote>
- <big>$(HIDESH) $(CLAM_DIR)/postconditions.sh<br>
+ <big>$(HIDESH) $(CLAM_SCRIPTS)/postconditions.sh<br>
</big>
<blockquote><big>This runs a shell script that handles the end
portion of a
but this will trap errors it sees and play the build error
CLAM_ERROR_SOUND.<br>
</big>
- <h4><big>CLAM_BINARY_DIR</big></h4>
+ <h4><big>CLAM_BINARIES</big></h4>
<big> This is a folder where the helper
binaries for the CLAM makefile system are located. <br>
</big>
- <h4><big>CLAM_DIR</big></h4>
+ <h4><big>CLAM_SCRIPTS</big></h4>
<big> This variable points at the location
where the definitions and helper scripts are located. The
default is
repository
is also where source code and final products of compilation reside,
unless
- the default is over-ridden (see TARGETS_DIR).<br>
+ the default is over-ridden (see TARGETS_STORE).<br>
</big>
<h4><big>SH & SHELL</big></h4>
<big> These variables both point at a
Instead,
a generated variable called ACTUAL_TARGETS is used.<br>
</big>
- <h4><big>TARGETS_DIR</big></h4>
+ <h4><big>TARGETS_STORE</big></h4>
<big> This folder is where all generated
files are
to
for C++ header files (files ending in ?.h?).
</big>
<h4><big>HOOPLE_HEADERS</big></h4>
+<big>DEPRECATED</big>
<big> The two standard places to look for
headers
(the repository and the third party directory) are listed in this
variable.
</big>
<h4><big>HOOPLE_LIBRARIES</big></h4>
+<big>DEPRECATED</big>
<big> This is where our libraries are
located. It is usually a subdirectory called "lib" under the
repository
<big> The most frequent cause of this
problem is a
directory
- not being on your path. The compilation tools bin (~/hoople/bin)
+ not being on your path. The compilation tools bin (CLAM_BINARIES)
directory must be in
the PATH variable.
<br>