Seems likely that it's this change of mine. https://github.com/apache/qpid-cpp/commit/b18583a6c05d0bb8cb9502f0823d902e17b2410e
I'll try to reproduce and see if this really the cause. On Mon, Mar 19, 2018 at 12:28 PM, Robbie Gemmell <[email protected]> wrote: > I see the same thing on Fedora 26 too. There have been cmake-related > changes on qpid-cpp and qpid-proton masters in recent days, its not > immediately clear to me whether it is one or the other, or both. > > On 19 March 2018 at 17:15, Oleksandr Rudyy <[email protected]> wrote: > > Hi, > > > > Jenkins job Qpid-Broker-J-Python-Test started to fail due to an issue > > with building cpp broker. The job was building qpid-cpp broker > > successfully before 15th of March. > > > > The jobs installs proton into non-standard location and sets > > PKG_CONFIG_PATH as specified in qpid-cpp INSTALL.txt. > > > > However, cmake fails to find proton and reports the following error: > > > > CMake Error: The following variables are used in this project, but > > they are set to NOTFOUND. > > Please set them or make sure they are set and tested correctly in the > > CMake files: > > Proton_LIBRARY > > linked by target "amqp" in directory > > /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J- > Python-Test/qpid-cpp/src > > linked by target "qpidmessaging" in directory > > /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J- > Python-Test/qpid-cpp/src > > > > What is interesting, that when both qpid broker and proton have the > > same install prefix, proton is found successfully by cmake. > > > > > > I can change the job to build qpid and proton with the same install > > prefix, though, I would like to clarify whether the build scripts have > > been changed intentionally and setting of PKG_CONFIG_PATH as > > described in INSTALL.txt is not supported any-more. > > > > I built on Fedora 27. Jenkins job is running on Ubuntu. > > For both environments the same cmake error is reported with > PKG_CONFIG_PATH. > > > > Kind Regards, > > Alex > > > > --------------------------------------------------------------------- > > 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] > >
