They are called from the build system. Lines 63 through 74 of proton-c/CMakeLists.txt add a custom command to call both protocol.h.py and encodings.h.py as part of the build process. These scripts pick through the xml files and produce header files with useful #defines. The protocol.py module is imported by protocol.h.py as part of this.
We don't currently use transactions.xml yet, but it is part of the xml that comes with the spec. I expect we'll start using it as soon as we build out better transaction support in the APIs. --Rafael On Fri, Nov 1, 2013 at 6:23 AM, Fraser Adams <[email protected]>wrote: > Hi All, > I've been trying to stumble my way round the proton directory tree trying > to work out how the Cmakes hang together and the like. > > Now I can see protocol.h.py gets called but when I grepped for > protocol.py (grep -rH "protocol.py" .) I got: > Binary file ./proton-c/src/protocol.pyc matches > ./proton-c/src/.svn/all-**wcprops:protocol.py > ./proton-c/src/.svn/all-**wcprops:/repos/asf/!svn/ver/** > 1352267/qpid/proton/trunk/**proton-c/src/protocol.py > ./proton-c/src/.svn/entries:**protocol.py > > So it doesn't look like it's called from anywhere - same for protocol.pyc > > Similarly it looks like messaging.xml, transport.xml, security.xml are > only called from protocol.py and I can't see anywhere transactions.xml is > referenced? > > I guess it's possible that these are referenced via dynamically > constructed names that I can't see by grepping. > > > Curious to know if they are there for a reason or are currently redundant. > > (This is me looking in trunk ) > > cheers, > Frase > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
