Update from Kasper develop (31639647)

Note: build issue with log4cxx, set `Kommon_USE_Log4CXX=OFF`

CMakeLists.txt

@@ -104,8 +104,10 @@ endif()
 add_compile_options( -Wall -Wextra -Werror )
 
 # Only link in libraries that we actually need (but not for executables since it makes things slow)
-set(_target_type "$<TARGET_PROPERTY:TYPE>")
-add_link_options( $<IF:$<STREQUAL:"${_target_type}","SHARED_LIBRARY">,LINKER:--as-needed,LINKER:--no-as-needed> )
+if( NOT APPLE )
+    set(_target_type "$<TARGET_PROPERTY:TYPE>")
+    add_link_options( $<IF:$<STREQUAL:"${_target_type}","SHARED_LIBRARY">,LINKER:--as-needed,LINKER:--no-as-needed> )
+endif()
 
 # Enable some advanced options depending on build type
 if (CMAKE_BUILD_TYPE MATCHES Rel)
@@ -195,6 +197,10 @@ option( KASPER_USE_GSL "Build GSL dependent modules" ${GSL_FOUND} )
 
 if(NOT DEFINED KASPER_USE_VTK)
     find_package(VTK QUIET COMPONENTS vtkCommonCore)
+    find_package(X11 QUIET)
+    find_package(GLEW QUIET)
+    find_package(Freetype QUIET)
+    find_package(JsonCpp QUIET)
     if(VTK_FOUND)
         message("VTK was found and enabled automatically. Set KASPER_USE_VTK=OFF to change this.")
     endif()
@@ -304,16 +310,6 @@ message(STATUS
     "   or `${CMAKE_MAKE_PROGRAM_NAME} doc` to generate the documentation.\n")
 
 # Install common project files
-
-configure_file( KasperVersion.h.in ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.h @ONLY )
-install( FILES ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.h DESTINATION ${INCLUDE_INSTALL_DIR} )
-
-configure_file( KasperVersion.json.in ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.json @ONLY )
-install( FILES ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.json DESTINATION ${CONFIG_INSTALL_DIR} )
-
-configure_file( KasperVersion.xml.in ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.xml @ONLY )
-install( FILES ${CMAKE_CURRENT_BINARY_DIR}/KasperVersion.xml DESTINATION ${CONFIG_INSTALL_DIR} )
-
 configure_file( kasperenv.sh.in ${CMAKE_CURRENT_BINARY_DIR}/kasperenv.sh @ONLY )
 configure_file( create_kasper_user_directory.sh.in ${CMAKE_CURRENT_BINARY_DIR}/create_kasper_user_directory.sh @ONLY )
 install( PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/kasperenv.sh ${CMAKE_CURRENT_BINARY_DIR}/create_kasper_user_directory.sh DESTINATION ${BIN_INSTALL_DIR} )

Documentation/Bindings/README.md

@@ -0,0 +1,67 @@
+
+Bindings documentation
+======================
+
+This section provides documentation for the **XML bindings**. Many Kasper
+modules can parse XML files during intialization; the bindings classes define
+the available XML elements, their attributes and their relation to C++ classes.
+
+Overview
+--------
+
+The files below show the allowed *elements* and *attributes* that can be used
+in Kasper XML files; according to the syntax:
+```
+  <element attribute_1="value_1" attribute_2="value_2">
+    <child_element attribute_3="value_3" />
+  </element>
+```
+
+Elements can be nested according to what is shown here, and each element can
+have a number of attributes. Note that in some cases, certain child elements
+and attributes are required; in other cases, they are mutually exclusive. Note
+that this information is not represented here in the documentation.
+
+* **[bindings_full.md](bindings_full.md)** contains a Markdown representation
+  of the available bindings. The document is grouped into section that each
+  have a table with all XML elements and attributes. Each section also
+  includes a brief XML snippet as a usage example and links to child elements.
+* **[bindings_full.rst](bindings_full.rst)** contains the same representation
+  of the available bindings in reStructuredText (rST) format.
+* **[bindings_full.xml](bindings_full.xml)** contains all available bindings
+  and their attributes in XML format. The attributes contain placeholder values
+  which indicate their data type. This file is not intended to be processed
+  by Kasper applications, but servers as an almost-complete XML code example.
+* **[bindings_full.svg](bindings_full.svg)** contains a graphical
+  representation of the XML elements and their relations. The graph is produced
+  with the GraphViz software. The graph shows all relations between XML
+  elements and their C++ classes, but not their attributes. 
+* The following files contain a more detailed graphical representation of the
+  XML elements of individual Kasper modules along with their attributes:
+  * **[bindings_Kommon.svg](bindings_Kommon.svg)** for the `Kommon` module
+  * **[bindings_KaLi.svg](bindings_KaLi.svg)** for the `KaLi` module
+  * **[bindings_KGeoBag.svg](bindings_KGeoBag.svg)** for the `KGeoBag` module
+  * **[bindings_KEMField.svg](bindings_KEMField.svg)** for the `KEMField` module
+  * **[bindings_Kassiopeia.svg](bindings_Kassiopeia.svg)** for the `Kassiopeia` module
+  * **[bindings_KSC.svg](bindings_KSC.svg)** for the `KSC` module
+  * **[bindings_SSC.svg](bindings_SSC.svg)** for the `SSC` module
+  * **[bindings_KaFit.svg](bindings_KaFit.svg)** for the `KaFit` module
+
+Source script
+-------------
+
+The files in this directory can be autgenerated with a Python script
+[gen-bindings-docs.py](../../Scripts/gen-bindings-docs.py) which provides
+options to generate XML, Markdown (`.md`), reStructuredText (`.rst`), and
+GraphViz (`.dot`) files. The GraphViz files can be converted into image
+files (`.svg`). Run the script with the `--help` option to see all options.
+
+The shell script [gen-bindings-docs.sh](../../Scripts/gen-bindings-docs.sh)
+carries out all these individual steps and updates the files listed here.
+
+Bindings graph
+--------------
+
+This graph shows the available XML elements in Kasper and their relations:
+
+<img src="bindings_full.svg" width="800" >