-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/09/2015 01:26 PM, Ryan Pavlik wrote:
> It's for if your use case requires the project to be installed in
> a specific location that's not the automatically generated one.
> For instance, if you're building multiple external projects you
> might have them all install to the same subdirectory of the binary
> directory for convenience.
>
> Ryan
I personally believe that you should never use the files constructed
in the build directory. This can work for binaries or static libraries
but is a point of failure with dynamic libraries (often the relative
paths of those are different in the final install).
One case where installing is absolutely necessary (at least in my
somewhat limited experience); windows, which requires that all the
dynamic libraries used by a program to be in the smae install directory.
Hope it help a little.
Theo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlUmeb0ACgkQEr8WrU8nPV2U8QCeKO8ldeKUnQHktROVz1uzo0x6
ZDQAoJOL8KciN9pq5H+09tmSRhqSqiQ6
=J+yG
-----END PGP SIGNATURE-----
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
