The tex documents in the latex directory are used to create the CIPRES build notes compiled (from notes.tex) into notes.pdf (the pdf is kept under cvs control for those folks who don't want to use tex).

Please do not be intimidated by my fondness for introducing lots of tex commands.  
Just write plain comments in text if you have comments to make.



NOTE: compilation of the latex documents requires the (otherwise optional) listings package (and will soon require the algorithms package).
The general idea is to keep the components small so that they are processed by tex quickly during composition,
The conditional-preamble.tex documents assist composition by allowing you to tex each sub document by itself or include it using an \input command

Definitions of new commands (e.g. shortcuts or words or phrases that require special typesetting) should go in latex/preamble.tex (along with \usepackage statements).

I'm trying to put a comment at the beginning of each small document that explains what the document is about.  The form of these comments is evolving. Currently it is 3 lines; the comment fields are:
% <type of object described> <who it affects
% platform <platform>
% language <programming language>

The choices are (where the | below indicates an "or" in a choice):
% library|buildtool|app|bug maintainer|libuser|appuser
% platform linux|mac|*nix|win (*nix is assumed to apply to linux and mac)
% language C++ python Java all

I (MTH) was hoping that we can eventually use these tags for helping us find files that need to be included in any documentation vs documentation targetted at end users vs documentation for CIPRES library users.