We have a large-ish system. Deep within an included utility class, I have
this code:
CONFIGURE_FILE(${DCMTK_SOURCE_DIR}/osconfig.h.in
${DCMTK_BINARY_DIR}/include/dcmtk/config/osconfig.h)
However, every time I touch a CMake file, ³osconfig.h² is regenerated,
causing nearly the
On Tue, Jan 12, 2010 at 02:09:36PM -0600, Daniel Blezek wrote:
CONFIGURE_FILE(${DCMTK_SOURCE_DIR}/osconfig.h.in
${DCMTK_BINARY_DIR}/include/dcmtk/config/osconfig.h)
However, every time I touch a CMake file, ³osconfig.h² is regenerated,
causing nearly the entire library to
you shouldn't have to do that. There are multitudes of projects that
do exactly what you are doing and don't have continuous rebuilds. Now,
having said that I am _assuming_ that osconfig.h.in is NOT being
changed, generated, updated or in any way changed? osconfig.h.in being
changed would
Daniel Blezek wrote:
Hi Mike,
Sorry, I guess I wasn't quite clear. The re-builds occur when I touch any
CMakeLists.txt file in the entire project. Since we're under active
development, new source files are being added fairly frequently. I didn't
want re-builds to trigger each time a
Hmmm, I'll dig a little deeper to see what's hapening.
Thanks,
-dan
On 1/12/10 4:25 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
Daniel Blezek wrote:
Hi Mike,
Sorry, I guess I wasn't quite clear. The re-builds occur when I touch any
CMakeLists.txt file in the entire project.
