Summarizing the configuration choices

Once the configuration is properly made one can check the choices made by looking the little summary proposed by cmake. This summary should look like ([...] denotes eluded portions):

~/DIET > ./cmake ..
[...]
- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-- XXXXXXXXXXXXXXXXXXXXXX  DIET configuration summary  XXXXXXXXXXXXXXXXXXXXXX
-- XXXXXXXXXXXXXXXXXXXXXXXXXXX 2010/03/31-07:47:15 XXXXXXXXXXXXXXXXXXXXXXXXXX
-- XXX System name Linux
-- XXX - Install prefix: /home/diet/local/diet
-- XXX - C compiler   : /usr/bin/gcc
-- XXX    * version   : 4.3.4
-- XXX    * options   :  -Dinline="static __inline__" -Dconst="" -std=gnu99
-- XXX - CXX compiler : /usr/bin/c++
-- XXX    *  version  : 4.3.4
-- XXX    *  options  : -lpthread -g -D__linux__
-- XXX - OmniORB found: YES
-- XXX   * OmniORB version: 4.1.2
-- XXX   * OmniORB directory:
-- XXX   * OmniORB includes: /usr/include
-- XXX   * OmniORB libraries: [...]libomniDynamic4.so;[...]libomniORB4.so;[...]libomnithread.so
-- XXX - General options:
-- XXX   * Examples: ON
-- XXX   * BLAS Examples: ON
-- XXX - Options set:
-- XXX   * Batch: ON
-- XXX   * Statistics: ON
-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[...]

A more complete, yet technical, way of making sure is to check the content of the file named CMakeCache.txt (generated by cmake in the directory from which cmake was invocated). When exchanging with the developers list it is a recommendable practice to join the content of this file which summarizes your options and also the automatic package/library detections made by cmake.