Introduce build_visualization option #208
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our Institute we had the use case to build the rock workspace without visualizations.
Also, we realized that the existing manifest.xml files in the viz subfolders are not evaluated at all, even though there is one in the official template. Was this a feature of autoproj that was possibly lost when going from autoproj v1 to v2?
This PR introduces a configuration option to select globally if the viz folders should be build and also uses the viz/manifest.xml files to be able not to install dependencies only needed for the visualization.
This PR is meant to start a discussion on how to handle this situation the best way, e.g. we were unsure if we should actually ask for the option or just have a documentation on how to disable it by setting the config option directly.