that need to be used with CLAM. Several example makefiles and the
full
reference manual for CLAM are also included.<br>
that need to be used with CLAM. Several example makefiles and the
full
reference manual for CLAM are also included.<br>
and can be
downloaded from there or through a sourceforge mirror site.<br>
In the remainder of the document, we will often
and can be
downloaded from there or through a sourceforge mirror site.<br>
In the remainder of the document, we will often
<li><big>Setting environment variables for clam:</big></li>
<small> </small><big> </big><small> </small>
<ol>
<li><big>Setting environment variables for clam:</big></li>
<small> </small><big> </big><small> </small>
<ol>
- <li><big>The default location for clam is under the FEISTY_MEOW_DIR
- in a
- folder named clam, although the version of clam shipped with the
- HOOPLE
- code (http://hoople.org) actually lives under the root of the
- hoople
- hierarchy.<br>
+ <li><big>The default location for clam is under the FEISTY_MEOW_SCRIPTS directory in a
+ folder named clam.<br>
<ol>
<small> </small><big> </big><small> </small>
<li><big>On Unix (assuming bash as shell): <span style="font-weight: bold;">export
<ol>
<small> </small><big> </big><small> </small>
<li><big>On Unix (assuming bash as shell): <span style="font-weight: bold;">export
pre-built
versions of tools used by clam during a build.<br>
</big></li>
<small> </small><big> </big><small> </small>
<li><big>If you would rather rebuild them from source, then
running
pre-built
versions of tools used by clam during a build.<br>
</big></li>
<small> </small><big> </big><small> </small>
<li><big>If you would rather rebuild them from source, then
running
<small> </small><big> </big><small> </small>
<li><big>The standard source code repository is a directory
called
<small> </small><big> </big><small> </small>
<li><big>The standard source code repository is a directory
called
library archive in your home directory, you should be all set to
perform a build.</big></li>
<small> </small><big> </big><small> </small>
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
- downloading that codebase (<a href="http://hoople.org">http://hoople.org</a>).<br>
+ <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>
<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
<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
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
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
win32). There are three TYPEs supported so far: </big></p>
<ul>
<small> </small><big> </big><small> </small>
win32). There are three TYPEs supported so far: </big></p>
<ul>
<small> </small><big> </big><small> </small>
The include directory is created as a copy of the headers in the
project's
directory . Library projects will also have their final products
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
Projects that are of type "application" will
have their executables
copied to the executable directory in the repository (such as
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>
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> This is a folder where the helper
binaries for the CLAM makefile system are located. <br>
</big>
<big> This is a folder where the helper
binaries for the CLAM makefile system are located. <br>
</big>
<big> This variable points at the location
where the definitions and helper scripts are located. The
default is
<big> This variable points at the location
where the definitions and helper scripts are located. The
default is
<big> Specifies the root directory
for compilation or other building activities. The
repository
is also where source code and final products of compilation reside,
unless
<big> Specifies the root directory
for compilation or other building activities. The
repository
is also where source code and final products of compilation reside,
unless
<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> 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> This is where our libraries are
located. It is usually a subdirectory called "lib" under the
repository
<big> This is where our libraries are
located. It is usually a subdirectory called "lib" under the
repository
<small> </small><big> </big><small> </small>
<p><big><tt>include cpp/rules.def</tt></big></p>
<small> </small><small></small>
<small> </small><big> </big><small> </small>
<p><big><tt>include cpp/rules.def</tt></big></p>
<small> </small><small></small>