lcio/doc
diff -u -r1.56 -r1.57
--- versions.readme 26 Apr 2007 16:47:47 -0000 1.56
+++ versions.readme 13 Jul 2007 15:29:58 -0000 1.57
@@ -3,6 +3,14 @@
---------------------------------------------------------------
=====================
+v01-08-03
+=====================
+ bug fix release
+ no changes in file format and API
+ - minor fixes in Java code (TJ,JMC)
+ - full support for building with cmake
+
+=====================
v01-08-02
=====================
bug fix release
lcio/src/latex/manual
diff -u -r1.41 -r1.42
--- manual.tex 6 Jul 2007 12:38:52 -0000 1.41
+++ manual.tex 13 Jul 2007 15:29:58 -0000 1.42
@@ -111,38 +111,47 @@
AID~\cite{ref_aid} tool. The build scripts used in LCIO also require that \verb$gcc$ and
\verb$gmake/make$ are installed.
-The C++ version of LCIO is developed under (Suse) Linux with gcc2.95.3 and tested
-as well with gcc3.2 on Linux and Windows/Cygwin.
+The C++ version of LCIO is developed and tested under SL3 and SL4
+and builds under Windows/Cygwin and MacOSX.
+
As the -ansi switch is used it should be fairly easy to port it to other platforms with
an ANSI compliant C++ compiler.\\\\
-A new cross-platform building tool called CMake~\cite{ref_cmake} was introduced in LCIO
-version 1.8.3 for making the LCIO building system more compatible across different platforms
-and to also ease the task of maintaining it.\\
-Some of the features CMake includes are:
-\begin{verbatim}
- * Support for building shared libraries
- * Generates native build files (e.g., makefiles on Unix; workspaces/projects on MS Visual C++)
- * Support for out-of-source builds. Multiple build trees are possible from a single source tree.
- * CMake is open source
-\end{verbatim}
+
+\subsection{Building LCIO} \label{build_lcio}
+
+There are two build tools that can be used to build LCIO: ant and CMake~\cite{ref_cmake}.
+CMake~\cite{ref_cmake} has been introduced in version v01-08-02 to facilitate cross plattform support for
+the C++ version. Building LCIO with CMake is the preferred way within the LDC ilcsoft framework, however
+the {\em classic} way of building LCIO with ant is still fully supported, in fact CMake also uses the ant commands for Java and
+for generating the documentation.
+
+\subsubsection{Building LCIO with CMake}
If you want to use CMake for building LCIO you need at least CMake version 2.4.6.
-\subsection{Build LCIO} \label{build_lcio}
-If you want to build LCIO using CMake just follow these simple steps:\\\\
-1st: make sure that cmake is in your path:\\
+
+%Some of the features CMake includes are:
+%\begin{verbatim}
+% * Support for building shared libraries
+% * Generates native build files (e.g., makefiles on Unix; workspaces/projects on MS Visual C++)
+% * Support for out-of-source builds. Multiple build trees are possible from a single source tree.
+% * CMake is open source
+%\end{verbatim}
+
+If you want to build LCIO using CMak make sure that the cmake command is in your path, e.g.\\
+
\verb|export PATH=Path_to_CMake/bin:$PATH|\\\\
-2nd: edit the file BuildSetup.cmake and adjust it to your needs\\\\
-Afterwards type:
+
+then edit the file BuildSetup.cmake and adjust it to your needs, e.g specify that LCIO should be built with CLHEP support\\\\
+
+The issue the following commands:
\begin{verbatim}
- mkdir build <-- create an out-of-source directory for the build
+ mkdir build # <-- create an out-of-source directory for the build
cd build
cmake -C ../BuildSetup.cmake ..
make install
\end{verbatim}
-If for some reason you cannot use CMake for building LCIO there is still the possiblility
-to use the old makefiles (see below), but I strongly disencourage you to do so!\\\\
---- Deprecated!! ---
-For building LCIO with the old makefiles:\\
+
+\subsubsection{Building LCIO with ant}
A few variables have to be set depending on your development environment, e.g.
\begin{itemize}
@@ -224,7 +233,9 @@
\end{verbatim}
-This will create the following libraries and executables:
+
+
+Both ways of building LCIO will create the following libraries and executables:
\begin{verbatim}
./lib
