My suggestion is to edit the src/config.h before building to specify
the QPIDC_MODULE_DIR path on the target system. (I thought there would
be a way of setting it automatically via a cmake variable but I can't
seem to do that).
On Mon, Jun 21, 2021 at 5:38 PM rahul.sin...@morganstanley.com
wrote:
Hello,
Many thanks for your response. I build apache qpid libraries and my application
on a different compile machine and run my application on a different test
machine. Test machine does not have access to location used on compile machine.
While building my application, I point it to the local
On Mon, Jun 21, 2021 at 9:53 AM Ken Giusti wrote:
> Folks,
> If there are no objections I'd like to spin up an RC1 for the 1.16.1 patch
> release today.
>
+1, Sounds good. Thanks.
> thank,
> -K
>
>
> On Thu, Jun 17, 2021 at 9:48 AM Ken Giusti wrote:
>
> >
> >
> > On Thu, Jun 17, 2021 at 4:33 AM
Folks,
If there are no objections I'd like to spin up an RC1 for the 1.16.1 patch
release today.
thank,
-K
On Thu, Jun 17, 2021 at 9:48 AM Ken Giusti wrote:
>
>
> On Thu, Jun 17, 2021 at 4:33 AM Robbie Gemmell
> wrote:
>
>> I'm glad to see a followup release being done, but I find it
>> surpri
You should not need to have any client module directory. My first
guess is that it is perhaps a permissions issue. Is your application
running as a user able to list files under the
/lib64/qpid directory?
(The exception seems to come from stat() returning an error other than ENOENT).
On Mon, Jun
Hello,
I am trying on run my C++ application on linux based on QPID AMQP messaging API
and connect to TCP endpoint with SSL authentication. At the moment, I am just
trying to test the correct usage and do nothing more than establishing the
connection. However, I get a runtime error which indicat
