Hi again,
My project is set up so that the compiled targets naturally get output to a
structure that looks like a "development mode" installation:
/myproj
/build
/bin
/lib
/include
This is convenient for some users ... it is the sort of code people tinker
with, and I think a lot of my users will actually want to keep it local. I will
offer a more typical install as well.
In addition, I have some python and shell scripts mixed in with my source code
in subdirectories. These don't naturally get moved anywhere during the build
and I would like to do so to complete the "development installation" idea:
/myproj
/build
/bin
/lib
/include
/scripts
something.sh
/pylib
scripts and python shared libraries
How is this best done? Should I treat this as a case of "install"? In that case
when development mode is on I would install to the local directory. Strangely,
for 90% of the project the source and destination will be the same - which is
what makes it seem weird. Or should I just use "command" with cmake -E style
copying locally and only use install for the system install?
It may be that either will work, but it seems from my last post or two that I
don't always see the usual idioms and it could be neither of my guesses is a
good one.
Thanks,
Eli
--
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
