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 ..
[...]
 - Install prefix: /home/diet/local/diet
 - OmniORB found: YES
   * OmniORB directory: /home/diet/local/omniORB-4.0.7
   * OmniORB includes: /home/diet/local/omniORB-4.0.7/include
   * OmniORB libraries: /home/diet/local/omniORB-4.0.7/lib/libomniDynamic4.so;
     [...]libomniORB4.so;[...]libomnithread.so;[...]libCOS4.so;[...]
 - General options:
   * Documentation: ON
   * Dynamics Libraries: ON
   * Examples: ON
   * BLAS Examples: ON
 - Options set:
   * Batch: ON
     -- Appleseeds directory: /home/diet/local/appleseeds-2.2.1
     -- Appleseeds includes:  [...]appleseeds-2.2.1/include/appleseeds
     -- Appleseeds library:   [...]appleseeds-2.2.1/lib/libappleseeds.a
   * CORI: ON
   * Dart: ON
   * JXTA: ON
   * JuxMem: ON
[...]

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.