This is a discussion ticket for us to brainstorm solutions.
There are 2 things in our ecosystem that we'd like to be able to share across multiple protocol libraries:
Both of these would require compiling components into a separate shared library, and then referencing them from within another schema.
In C, this means that the you have to include another schema's header file in your header file and then have your shared library dynamically link to the dependency library.
In Java this means you have to declare the additional dependency in your POM, and then load 2 shared libraries at runtime.
In C#, I assume this means you have to reference the dependency in XML when building the parent assembly and then pinvoke takes care of loading both libraries.
This is a discussion ticket for us to brainstorm solutions.
There are 2 things in our ecosystem that we'd like to be able to share across multiple protocol libraries:
Both of these would require compiling components into a separate shared library, and then referencing them from within another schema.
In C, this means that the you have to include another schema's header file in your header file and then have your shared library dynamically link to the dependency library.
In Java this means you have to declare the additional dependency in your POM, and then load 2 shared libraries at runtime.
In C#, I assume this means you have to reference the dependency in XML when building the parent assembly and then pinvoke takes care of loading both libraries.