Well basically, if you are on windows cmake can find the .lib file but then I wrote some code for each 3rd party library that attempts to find the .dll files. Once those files are found I create the copy files targets for each DLL.
Mike Jackson On Oct 27, 2014, at 11:17 PM, J Decker <d3c...@gmail.com> wrote: > how does that work with say openwatcom? > > On Mon, Oct 27, 2014 at 7:51 PM, Michael Jackson > <mike.jack...@bluequartz.net> wrote: > I use a copy rule for the DLLs during the build which finds the DLL and then > copies it to the Debug or Release directory. You are welcome to the macro > that we use for our project. If there is an easier way with Cmake 3.0.x I > would love to hear about it. > > Thanks > Mike Jackson > > > On Oct 27, 2014, at 9:55 PM, Robert Dailey <rcdailey.li...@gmail.com> wrote: > > > This actually used to be a very difficult problem to solve. However, > > to debug in visual studio it's essential. > > > > If I have DLLs located in third party directories OR from targets that > > I depend on, those must all be copied to the directory of the > > executable I'm debugging in order for those DLLs to be found and > > loaded. > > > > Using CMake 3.0.2, I hope this task is simpler, especially with the > > introduction of a nice suite of generator expressions. Can anyone > > recommend a good way to do this? > > -- > > > > 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 > > -- > > 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 >
-- 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
