Aaron,
it's about the way that you compile your binary and link libmysqlclient
into it. I guess (@all: please correct me if I am wrong) as I don't know
how you use cmake to build your libraries/binaries, that you don't set
the rpath of libmysqlclient inside your binary. Doing so will ensure
that the absolute path of libmysqlclient is stored into your binary, so
that the runtime environment can pick it up and use (keeping fingers
crossed that the path is still valid). The alternative to doing so, is
linking against the static version of libmysqlclient (which comes at a
cost on another front as well).
Best,
P
--
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
