On 7/1/2014 3:37 PM, Rick McGuire wrote:
The big question comes down to "should I?". Is doing this somehow a
violation of CMake rules/conventions? Are there any issues I
need to
consider? And, the ultimate question is whether it is somehow
possible
to set up dependencies where I could get back to the original build
behavior? Although I would be perfectly fine just having a
target that
allowed updating those files on demand.
So, yeah it is a bad idea to put files in the source tree from the
build. This will preclude multiple out of source build trees from
one source checkout. I like to think that the source tree is on a
read only file system.
There's really no problem with that, unless the developer is doing
something silly like trying to do simultaneous builds...and there are
other reasons that would preclude trying to do that.
It all depends on what is going into the source tree. Maybe not in
your specific case, but in general it is a bad idea to put files into
the source tree. The main reason is that it prevents clean out of
source builds.
-Bill
--
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