doublefox1981 wrote:
i get the latest version of qpid for cpp, and compile on windows follow by INSTALL-WINDOWS, but some error.

it says qpid::client::SessionImpl not define.

then i compile on linux, some error also,but it says " “qpid/sys/LatencyMetric.lo 
........“qpid/sys/LatencyMetric.cpp", may LatencyMetric.cpp not find
It appears that files were removed in revision 765285 but they are still referenced in cpp/src/Makefile.am. If those references are removed, the build still fails (on Fedora) with the following error:

g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -DMODULE_DIR=\"/usr/local/lib/qpid/client\" -DCONF_FILE=\"/usr/local/etc/qpid/qpidc.conf\" -g -O2 -MT gen/qpid/client/no_keyword/libqpidclient_la-AsyncSession_0_10.lo -MD -MP -MF gen/qpid/client/no_keyword/.deps/libqpidclient_la-AsyncSession_0_10.Tpo -c gen/qpid/client/no_keyword/AsyncSession_0_10.cpp -fPIC -DPIC -o gen/qpid/client/no_keyword/.libs/libqpidclient_la-AsyncSession_0_10.o gen/qpid/client/no_keyword/AsyncSession_0_10.cpp: In member function 'qpid::client::Completion qpid::client::no_keyword::AsyncSession_0_10::executionSync(bool)': gen/qpid/client/no_keyword/AsyncSession_0_10.cpp:40: error: invalid use of incomplete type 'struct qpid::client::SessionImpl' ./qpid/client/FutureResult.h:34: error: forward declaration of 'struct qpid::client::SessionImpl' gen/qpid/client/no_keyword/AsyncSession_0_10.cpp: In member function 'qpid::client::Completion qpid::client::no_keyword::AsyncSession_0_10::executionResult(const qpid::framing::SequenceNumber&, const std::string&, bool)': gen/qpid/client/no_keyword/AsyncSession_0_10.cpp:46: error: invalid use of incomplete type 'struct qpid::client::SessionImpl'
.
.
.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to