[CMake] Not hardcoding install dir in Config.cmake.

[Stephen Kelly]

Chris Dembia wrote:

> Hey all:
> 
> I work on a project that is used heavily on Windows. Our project also
> creates a Config.cmake file. During build time, we do not know where the
> project will actually be installed on the user's system. However, the
> Config.file needs to know the installation directory of the package.

I'm curious why that's needed? I guess it's for things like include 
directories? You might consider creating IMPORTED targets instead and 
encoding the include directories into those instead.

 http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#creating-packages

Thanks,

Steve.