Eric Noulard said:
> Instead of copying you could use
> cmake -E create_symlink
> but this won't work on Windows.
If building on Windows is required, you could make a symlink, hardlink, or
junction point. If on Vista or later, look at the command mklink. Symlinks
require admin privileges, but I
Hey Matthew.
I'm actually doing the latter. I setup my working directory in Visual
Studio project settings. I also setup add_test() to default to that
data directory when running them from ctest. Note that the tests also
need access to data, which is why they also have this logic.
On Thu, Mar 14,
2013/3/11 Robert Dailey :
> I have setup all of my compiled binaries to be placed in
> /output. Certain executables need to access data files
> relative to the executable's current position. When I'm debugging
> through visual studio, it cannot access the data unless I setup a
> post-build event to
One solution is to use CONFIGURE_FILE to produce a my_data_path.h file that
contains a #define to the data dir.
--
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:
I have setup all of my compiled binaries to be placed in
/output. Certain executables need to access data files
relative to the executable's current position. When I'm debugging
through visual studio, it cannot access the data unless I setup a
post-build event to copy the data to the 'output' direc
