OK... So on a completely fresh checkout (it seems like it doesn't deal very well with having some remenants of an old build on automake somewhere - even though I blew away everything I could see)...
it gets a lot further, but then dies with the following: inking CXX shared library libsslcommon.so CMakeFiles/sslcommon.dir/qpid/sys/ssl/check.o: In function `qpid::sys::ssl::ErrorString::ErrorString()': check.cpp:(.text+0xd): undefined reference to `PR_GetError' check.cpp:(.text+0x1a): undefined reference to `PR_GetErrorTextLength' check.cpp:(.text+0x3f): undefined reference to `PR_GetErrorText' CMakeFiles/sslcommon.dir/qpid/sys/ssl/util.o: In function `qpid::sys::ssl::promptForPassword(PK11SlotInfoStr*, int, void*)': util.cpp:(.text+0x3b8): undefined reference to `PL_strdup' CMakeFiles/sslcommon.dir/qpid/sys/ssl/util.o: In function `qpid::sys::ssl::readPasswordFromFile(PK11SlotInfoStr*, int, void*)': util.cpp:(.text+0x4b9): undefined reference to `PL_strdup' CMakeFiles/sslcommon.dir/qpid/sys/ssl/util.o: In function `qpid::sys::ssl::initNSS(qpid::sys::ssl::SslOptions const&, bool)': util.cpp:(.text+0x58a): undefined reference to `PK11_SetPasswordFunc' util.cpp:(.text+0x59b): undefined reference to `PK11_SetPasswordFunc' util.cpp:(.text+0x5b6): undefined reference to `NSS_Init' util.cpp:(.text+0x6a7): undefined reference to `NSS_SetExportPolicy' util.cpp:(.text+0x779): undefined reference to `NSS_SetDomesticPolicy' util.cpp:(.text+0x86c): undefined reference to `SSL_ConfigServerSessionIDCache' CMakeFiles/sslcommon.dir/qpid/sys/ssl/util.o: In function `qpid::sys::ssl::shutdownNSS()': util.cpp:(.text+0x93b): undefined reference to `NSS_Shutdown' CMakeFiles/sslcommon.dir/qpid/sys/ssl/SslSocket.o: In function `qpid::sys::ssl::SslSocket::SslSocket(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool)': ... and so on Presumably this is some SSL library incompatibility? -- Rob On 11 March 2013 17:02, Rob Godfrey <[email protected]> wrote: > Hmmm... > > it never gets far enough for the install prefix to make a difference > :-( (incidentally where is cmake mentioned in the docs - I can see it > in the windows README-winsdk.txt but not in README.txt which talks > exclusively about linux AFAICT) > > rob@humpy:~/qpid-trunk/qpid/cpp/build$ make clean > rob@humpy:~/qpid-trunk/qpid/cpp/build$ make > [ 1%] Building CXX object src/CMakeFiles/qpidtypes.dir/qpid/types/Exception.o > [ 1%] Building CXX object src/CMakeFiles/qpidtypes.dir/qpid/types/Uuid.o > [ 1%] Building CXX object src/CMakeFiles/qpidtypes.dir/qpid/types/Variant.o > Linking CXX shared library libqpidtypes.so > [ 1%] Built target qpidtypes > [ 1%] Building CXX object > src/CMakeFiles/qpidcommon.dir/qpid/framing/ExchangeBoundResult.o > /home/rob/qpid-trunk/qpid/cpp/build/src/qpid/framing/ExchangeBoundResult.cpp: > In member function ‘void > qpid::framing::ExchangeBoundResult::decode(qpid::framing::Buffer&, > uint32_t)’: > /home/rob/qpid-trunk/qpid/cpp/build/src/qpid/framing/ExchangeBoundResult.cpp:83:90: > error: ‘FramingErrorException’ was not declared in this scope > make[2]: *** > [src/CMakeFiles/qpidcommon.dir/qpid/framing/ExchangeBoundResult.o] > Error 1 > make[1]: *** [src/CMakeFiles/qpidcommon.dir/all] Error 2 > make: *** [all] Error 2 > > This is on an Ubuntu 12.04 64 bit system > > -- Rob > > On 11 March 2013 16:53, Michael Goulish <[email protected]> wrote: >> There are build instructions for linux and windows in the top-level >> README, but the cmake line only differs from what you are doing in >> its install prefix: >> >> cmake -DCMAKE_INSTALL_PREFIX=/usr .. >> >> >> >> >> >> ----- Original Message ----- >> So... apologies if I am missing them, but are there instructions as to >> how to build the C++ codebase using cmake? >> >> My experience with proton was that >> >> mkdir build ; cd build ; cmake .. ; make >> >> Would work... But that fails to compile with the C++ broker on my system. >> >> -- Rob >> >> On 11 March 2013 15:45, Gordon Sim <[email protected]> wrote: >>> On 03/09/2013 09:24 AM, Fraser Adams wrote: >>>> >>>> On 08/03/13 21:41, Andrew Stitcher wrote: >>>>> >>>>> . Anyway if it is anything the dev list is for discussion amongst the >>>>> qpid developers themselves (rather than developers who use qpid) and >>>>> surely they are the ons who "get to vote" about the build system. >>>> >>>> That's a fair point, but all I'm arguing for is good communication. So >>>> users don't get a vote - that's fine, but at least if they are able to >>>> register any worries about the potential impact then the scale of the >>>> short term support problem that might occur moving users who need to >>>> build qpid themselves will be better known. If we break something that >>>> users depend upon without communicating that fact then we risk pushing >>>> them away. >>> >>> >>> I agree completely. Issues that affect 'users' should be discussed on the >>> user list. The build system is absolutely one of those things (since the >>> Apache Qpid community only publishes source builds for c++). >>> >>> The lack of awareness of the reasons for moving to cmake and the eventual >>> removal of autotools is probably itself a result of a failure to adequately >>> inform users of plans. >>> >>> I am in support of Alan's proposal and agree with Fraser that we need to >>> communicate with users. As far as I understood it, the proposal was to >>> remove autotools *after* 0.22, not for it. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
