Hi, On Tue, Oct 9, 2012 at 5:39 PM, Fabio Fracassi <fabio.fraca...@charite.de> wrote: > On 10/9/12 5:05 PM, Andreas Pakulat wrote: > On Tue, Oct 9, 2012 at 4:42 PM, Fabio Fracassi > What do you mean with "package registry" here? > > It means the package registry where cmake stores previously build packages, > which can be disabled with NO_CMAKE_PACKAGE_REGISTRY and is located in > ~/.cmake/packages/<name>/* and which is searched as the 6th point.
Ah, never came across that part before. What happens if you explicitly disable searching the package registry? > Does that mean the > files installed into /usr/local/ reference the builddir? If that is > the case then you probably didn't generate the config files properly. > Can you post the generated files as well as the corresponding > install(EXPORT) and install(TARGETS ... EXPORT) lines? > > No, those are ok, and indeed work if I manualy point to the installed dir. > It is just that for some reason CMake prefers > ~/build/<MyLibrary>/<Mylibrary>-config.cmake over > /usr/local/lib/CMake/<MyLibrary>/<Mylibrary>-config.cmake Hmm, at this point I'd probably try cmake --trace and/or --debug-outpu and maybe also the output of --system-information to find out why cmake decides to load the config file from that location. Oh and I assume that your client thats using the config has its own build-directory, i.e. something like ~/build/<client>/ and there's no CMakeCache.txt in ~/build/ Andreas -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
