Hello, I haven't look deeper but it would be really great if you can help locating where actually the generated code gets in. Does it go under the install directory or the source directory where we have qpid-cpp-1.39.0 folder.
Best Regards, Rahul -----Original Message----- From: Gordon Sim <g...@redhat.com> Sent: 09 July 2021 15:29 To: users@qpid.apache.org Subject: Re: Ruby requirements for QPID C++ On Fri, Jul 9, 2021 at 12:39 PM rahul.sin...@morganstanley.com <rahul.sin...@morganstanley.com> wrote: > Building qpid-proton is fine without Ruby. However, when I try to > build qpid-cpp-1.39.0, cmake gives below error - > > CMake Error at src/CMakeLists.txt:87 (message): > Can't locate ruby, needed to generate amqp 0-10 framing code. > > Though I need it for AMQP 1.0. > I use the same install folder as I did for qpid proton. Also, I exported the > PKG_CONFIG_PATH. > > Once I add Ruby module, then it works happily and later on detects that AMQP > 1.0 is enabled. Unfortunately building the 0-10 code is not optional at present. However if the generated code is there then it doesn't need to be regenerated. (You would still get an error, but that could be disabled with the attached patch). So if you had to build somewhere that didn't have ruby you could bundle up and reuse source generated from somewhere you do have ruby. Or if you want to remove it after generation, you could do that also. -------------------------------------------------------------------------------- NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers If you cannot access these links, please notify us by reply message and we will send the contents to you. By communicating with Morgan Stanley you consent to the foregoing and to the voice recording of conversations with personnel of Morgan Stanley. You may have certain rights regarding the information that Morgan Stanley collects about you. Please see our Privacy Pledge https://www.morganstanley.com/privacy-pledge for more information about your rights.
