On 3/26/10 9:40 AM, Brad King wrote:
[email protected] wrote:
One thing you can do with one directory full of .exe and .dll files is
to copy it somewhere else—to an arbitrary directory on another computer,
Perhaps the install() command is better for that.
-Brad
What I've done for develop-time handling of DLL search path, etc. is to
write a CMake module with a function that effectively just generates a
.cmd (or .bat or .sh) file that changes the current directory, prepends
the DLL directories to the PATH environment variable (on windows, or
LD_LIBRARY_PATH on Linux...) then runs the executable. If you include
the "change directory" line, you could effectively put this generated
script anywhere after creating it.
Ryan
--
Ryan Pavlik
Human-Computer Interaction Graduate Student
Virtual Reality Applications Center
Iowa State University
[email protected]
http://academic.cleardefinition.com/
_______________________________________________
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
