How to build a dynamic_opentracing plugin for Envoy

[Oberon00]

Description:
In issue #4140 it is mentioned that a "A specific build process is required for the dynamic loading [of opentracing plugins] to work.". Is there any documentation of this build process? Are independent vendors even supposed to provide binary opentracing plugins for envoy? Background: I want to build such a plugin, and am thinking about what the best way to package or deploy it would be.

Relevant Links:
PR #2252
Issue #4140

[mattklein123]

@rnburn would be great to get some docs on this or if there are docs better links?

[rnburn]

Envoy statically links in the standard C++ library by default. The specific build process is referring to the additional steps that need to be taken to work with a statically linked standard library. (See this SO post for background).

Basically what you need to do is to use a version script when linking to keep symbols from being exported. You can look at Jaeger's build-plugin.sh script to see an example of how to set it up.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.