Enable loading a render engine plugin from the static plugin registry #1152
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.
🎉 New feature
Summary
Extends
RenderEngineManager
to load a render engine plugin from the static plugin registry.Also registered the default render engine plugins based on lookup in the plugin registry at runtime, in case one or more of the default render engines were statically linked in. This is required so that
unloadEngine()
can correctly unload the instantiated engine using the standard name, e.g. "ogre2". (Note:unloadEngine
is called from thegz::sim::Sensors
system). To make the plugin filename in the static plugin registry more obvious, I also added aliases for the existing render engine plugins with fully qualified names.Test it
Added a test in the bazel build:
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
andGenerated-by
messages.