Documents the add_celix_container USE_CONFIG option
@@ -176,6 +176,7 @@ Use the `<celix_container_name>` executable to run the deployments.
add_celix_container(<celix_container_name>
[COPY]
[CXX]
+ [USE_CONFIG]
[GROUP group_name]
[NAME celix_container_name]
[LAUNCHER launcher]
@@ -187,7 +188,7 @@ add_celix_container(<celix_container_name>
- If the COPY option is provided the selected bundles will be copied in a bundles dir and the generated config.properties will use relative paths to the bundle locations. Default bundles will not be copied and the generated config.properties will use absolute references to the bundle locations.
- If CXX option is provided the celix container launcher will be build as C++ executable and as result be linked with the required C++ libraries of the used compiler.
-- If USE_CONFIG option is provided a config.properties file will be generated next to the executable. The config.properties contains the configuration for provided BUNDLES and PROPERTIES.
+- If USE_CONFIG option is provided a config.properties file will be generated next to the executable. The config.properties contains the configuration for the provided BUNDLES and PROPERTIES.
- If GROUP is provided the celix container will be grouped in the provided group name.
- If NAME is provided that name will be used for the celix container dir. Default the Celix container target name will be used.
- If LAUNCHER is provided that path or target will be used as launcher executable for the Celix container. If no LAUNCHER is not provided the celix executable will be used.
