[CastXML] CastXML Dynamic Shared Object extensions?

[Brad King]

On 07/20/2018 04:24 PM, Steve Coleman wrote:
> A member of my team that knows our current implementation well was 
> saying that some tagged xml attributes was done differently in gccxml. I 
> am therefore trying to learn whatever I can about the new CastXML parser 
> design changes/considerations within the new tool, so that we can bridge 
> any gaps in their capability, at least as far as we have been using it.

CastXML's `--castxml-gccxml` option activates the gccxml-like output
format.  It's intended to be much like the original gccxml output but
making it 100% byte-for-byte identical is not a goal.  Most clients should
be easy to port.  There is also a `--castxml-output=1` option that updates
the output format in a way that requires a few more client changes but
fixes a few things.

> Right now I am digging around for documentation and resources to wrap my 
> brain around "what is possible" using the new tool. I came across the 
> "--dsopath" option but have been unable to find anything discussing what 
> this option provides in terms of extending the built in capabilities of 
> CastXML.

Almost all of castxml's options start in `--castxml-`.  The rest of the
options in the `--help` output come from the underlying clang.  The
`--dsopath` must be one of the latter.  CastXML has no support for
plugins to the output generator.

-Brad