[This refers to changes QPID-5632 and PROTON-536 which were commited to trunk and should appear in Qpid 0.28 and Proton 0.7]
I've added some cmake config files to the files that qpid/proton install so that in the usual case (for installed packages) you should be able to just use the usual find_package(Qpid) or find_package(Proton) Commands to detect whether or not they are present on the system. The usual other options for find_package should also apply - eg checking for specific versions of the packages etc. [I chose that capitalisation because it looks like that is how most other packages are named in cmake.] Cmake should automatically pick up the system installed version of the config files and it will also pick packages already installed in to the install prefix (as specified by CMAKE_INSTALL_PREFIX). If you are using qpid or proton in a different place then the best way to tell cmake where to look is to add the package install prefix to CMAKE_PREFIX_PATH. Because cmake will automatically look in the install prefix I now recommend that if you have your own custom proton and qpid installs you use the same install prefix for both and just build/install proton first, viz: cd <bld location of proton> cmake -DCMAKE_INSTALL_PREFIX=<install prefix> ...<other cmake options> <make> install cd <bld location of qpid c++> cmake -DCMAKE_INSTALL_PREFIX=<install prefix> ...<other cmake options> <make> install Note that the existing pkgconfig files are unchanged, so if you were using pkg config to detect proton or qpid you won't be affected. However if you were using cmake for your build system you now have another (simpler and a preferred) way to detect/configure proton/qpid. Questions comments to me here. Bugs to Jira. Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
