Regarding Anjuta & STK settings

For a while you will receive programming assignments as project files.
These include not only the source code on which the assignment is based,
but also all related settings that Anjuta and STK need.
If your understanding of an IDE like Anjuta and a toolkit like STK is
already quite advanced, you may want to know what the seetings are to 
start writing your own code independently. To tweak those, go to...

Anjuta:Settings:Compiler and Linker Settings: and select the following tabs:

Include Paths
- browse to the STK directory and add the <include> directory within
Library Paths
- browse to the STK directory and add the <src> directory within
Libraries
- write and press add (one at a time): asound, stk, pthread
Defines
- write and press add (one at a time): __LINUX_ALSA__, __LITTLE_ENDIAN__

You may also want to set your working directory for projects, goto...

Anjuta:Settings:Preferences: and select the General tab

set the Project directory, and (optionally) correct your e-mail

One final step, be sure that the executable can link to the rawwaves directory in STK.
If you base your work in the <projects> folder, next to the <stk> directory, then you
should create a symbolic link like this: ln -s ../stk-4.0/rawwaves/ . inside <projects>

The source code you are about to execute should reside 2 directory levels down
(a subfolder of a subfolder within <projects>, because that is specified inside
stk-4.0/src/Makefile in the RAWAVES variable).

A typical structure tree in our assignments follows this convention, because every assignment
inside <projects> contains another folder with the actual name of the project, thus 2 levels down.

i.e. ~/220/projects/assignment2/click/<project files>


After all this, any code C++ and STK compliant should compile (F10) and execute (F3).

* This is not a required procedure now as this information will be explained in class 
and you are being handed the project files ready to run *
** Also, in the next release of STK most of this steps will become invisible to the user,
handled by a config file which will locate what it needs during installation!  **