On Thu, 2013-08-01 at 13:30 +0200, Jakub Scholz wrote: > Hi, > > I think the Python is needed only at the build time for generating some > parts of the code. I do not think you need it at runtime.
For obscure reasons the build process actually requires both python and ruby for code generation at build time. Actually I think that only ruby is required for building the C++ client libraries, however the build process may not correctly adapt if no python is available as python is required as part of the build time testing. As others have said there is no run time dependency on either ruby or python in the C++ API libraries (unless you want the ruby or python APIs) Andrew > > Regards > Jakub > > > On Thu, Aug 1, 2013 at 1:24 PM, yonexw <zw...@liquidcapital.com> wrote: > > > Hi All, > > > > I am trying to build qpid C++ client apid, when I configure it I found it > > will use python. And I am sure I won't use python in my program. Why python > > is need in client C++ API, and how can I disable it when build qpid C++ > > client api? > > > > Thanks a lot! > > > > > > > > > > > > -- > > View this message in context: > > http://qpid.2158936.n2.nabble.com/How-to-build-qpid-C-client-API-without-python-tp7596285.html > > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
