Adam Mitz

Please see sections 7.4.1 and 7.4.2 of the OpenDDS Developer's Guide for general descriptions of the how the transports work and 7.4.5.6 for shared memory in particular.

Since GitHub Actions are integrated into GitHub's UI, I think we can go without adding to the README

Something like this has been discussed, but it may be too much of a change to take on within 3.x. If `opendds_idl` is treated as a "driver" (much like a...

All libraries that are used (even indirectly) will be listed to support static builds. There is no downside to including them in shared builds since they need to be present...

As a user you are free to build without OpenDDS_InfoRepoDiscovery and the list will be smaller. The test is set up to be more flexible so that different configurations can...

What is the problem with linking to libraries that must be present on the system?

I don't know if we have a way to move forward on this issue. The way libraries are used is "by design." If you want to propose something different that...

The compiler writes them for us. If there's example client code that doesn't work, please add a test and we'll fix it.

Then we would get feedback that there are too many lines of code generated

https://issues.omg.org/issues/lists/dds-xtypes-rtf#issue-45489