Compiling and installing DIET with cmake (version 2.2.3 or higher) :

I/ For the (really) impatients:
  cd ..        [ relative to this README file i.e. cd the home of DIET sources ]
  mkdir dietbin
  cd dietbin
  ccmake .. -DCMAKE_INSTALL_PREFIX:PATH=/tmp -DDIET_USE_CORI:BOOL=ON
    [ deal with the interface options: help is at bottom of screen! ]
  make
  make install

II/ Generating the Makefiles:
  CMake provides two ways for setting configuration parameters in order to
  generate the Makefiles:
   - ccmake [options] <path-to-source>
     specify the parameters interactively through a GUI interface
   - cmake [options] <path-to-source> [-D<var>:<type>=<value>]
     specify the parameters on the command line ( cmake -i [*] = ccmake [*] ).

  For both commands:
   - <path-to-source> specifes a path to the top level of the source tree
     (where the top level CMakeLists.txt file is to be encountered),
   - the current working directory will be used as the build tree for
     the  project. Out of source building is generaly prefered (specially
     when working on a CVS tree).
  
  ccmake interface tips:
   - look for the bottom of the interface were ccmake shortcuts are recalled,
   - moving up/down the paramater list with up/down arrows keys
   - hitting h on a parameter pops up the documentation for that parameter
     and general ccmake documentation and keyboard shortcuts (hit e to exit)
   - hit t for displaying cmake advanced parameters
   - when editing a PATH parameter the <TAB> key provides the "usual"
     (for emacs or bash users) automatic path completion

  cmake internal worth mentioning parameters:
   - CMAKE_BUILD_TYPE set to Debug for producing debugging information
   - CMAKE_VERBOSE_MAKEFILE set to ON will generate makefiles without
        the .SILENT directive (usefull for watching the invoked commands
        and their arguments)
   - CMAKE_C[XX]_FLAGS* for customized setting of C/C++ compiler options

III/ the DIET case:
   - assume CVS_DIET_HOME refers to the directory GRAAL/devel/diet/diet
     of a cvs checkout of the DIET sources hierarchy. CVS_DIET_HOME is
     the path to the top level directory of the DIET CMakeLists.txt hierarchy,
   - DIET CVS_DIET_HOME/Bin is a recommended out of source build directory,
   - The configuarion through the GUI goes:
     cd CVS_DIET_HOME/Bin
     ccmake ..
       * hit c (equivalent of bootstrap.sh)
       * Toggle/specify the following parameters
         CMAKE_INSTALL_PREFIX  (for avoiding default /usr/local)
         DIET_USE_JXTA
       * hit c for checking requires dependencies
       * While they are
         [
              (paramaters preceeded with a *)
           or (parameters whose value is terminated by NOT-FOUND)
         ]
         - provide the necessary information
         - hit c to configure
       * hit g to generate the makefile
       * hit q to exit ccmake
     make
     make install

IV/ DIET specific cmake parameters:
  - DIET_BUILD_DOCUMENTATION for ... building LaTeX-based user's guide,
    the developper's guide and the doxygenated documentation.
  - DIET_BUILD_EXAMPLES for ... building examples
  - DIET_BUILD_BLAS_EXAMPLES for ... BLAS based examples.
  - DIET_USE_BATCH for ... Appleseeds based batch extensions.
  - DIET_USE_CORI for ... a built-in low-profile FAST surrogate.
  - DIET_USE_FAST for ... using FAST a grid aware dynamic forecasting library.
  - DIET_USE_JXTA for ... using JXTA for dynamic MULTI Master Agent support.
  - DIET_WITH_MULTI_MA for ... MULTI Master Agent based support.
  - DIET_WITH_STATISTICS for ... good question, for what ?
  - OMNIORB4_DIR is the path to the omniORB4 installation directory
    (only relevant when omniORB4 was not installed in /usr/local).
    Example: cmake .. -DOMNIORB4_DIR:PATH=/usr/local/omniORB-4.0.7

V/ DIET [c]cmake invocation example:
 ccmake .. -DDIET_USE_CORI:BOOL=ON 
           -DDIET_BUILD_BLAS_EXAMPLES:BOOL=ON -DDIET_USE_FAST:BOOL=ON
           -DDIET_USE_JXTA:BOOL=ON -DDIET_WITH_MULTI_MA:BOOL=ON
           -DDIET_BUILD_DOCUMENTATION:BOOL=ON
           -DDIET_BUILD_EXAMPLES:BOOL=ON 
           -DOMNIORB4_DIR:PATH=/home/bozo/local/omniORB-4.0.7/
           -DCMAKE_INSTALL_PREFIX:PATH=/home/bozo/local/diet
           -DDIET_USE_BATCH:BOOL=ON
           -DAPPLESEEDS_DIR:PATH=/home/bozo/tmp/appleseeds-2.2.1/appleseeds
           -DFAST_CONFIG_EXECUTABLE:PATH=/usr/local/fast-0.8.7/bin/fast-config

VI/ Cmake general information, references and docs:
  Entry point:   http://www.cmake.org
  Official docs: http://www.cmake.org/HTML/Documentation.html
  Wiki docs:     http://www.cmake.org/Wiki/CMake
  FAQ:           http://www.cmake.org/Wiki/CMake_FAQ
  Google with the command your are looking for as key (avoid cmake as keyword).

VII/ Requirements:
  Obtain and install the lastest stable of cmake from http://www.cmake.org/
  (take at leat version 2.2.3).
  Although the various binary packages are not available on this site
  apt-get is generally cmake aware. By default fetching the sources,
  compiling and installing them should be straightfoward...

VIII/ Submitting ctest reports to Dashboard:
  Diet undergoes a nightly rebuild process which report can be found at
     http://graal.ens-lyon.fr:8081/DIETcore/Dashboard/
  If you wish to report your building (compile/linking/tests) to this
  public server, simply run the command (from the building tree):
     ctest -D Experimental
  The dashboard should display your report within 15' under the Experimental
  section...
