I have a question about knowing when you have run cmake enough times to
resolve all the cache variables for a project. In the CMake explanation
on the main website, regarding generation using the cmake.exe program
from the command-line in non-interactive mode, it says It can be
difficult to know
Luke Kucalaba wrote:
I have a question about knowing when you have run cmake enough times to
resolve all the cache variables for a project. In the CMake explanation
on the main website, regarding generation using the cmake.exe program
from the command-line in non-interactive mode, it says “It
of cmake works?
Luke
-Original Message-
From: Bill Hoffman [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 11:12 AM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] Running cmake multiple times to resolve cache
variables
Luke Kucalaba wrote:
I have a question about
Luke Kucalaba wrote:
I think the reason we need to run cmake.exe multiple times is because we
typically have a main project that automatically sets the options of
dependent projects. For example, our main executable project has an
option ENABLE_NETWORKING, which then triggers automatic changes
:[EMAIL PROTECTED]
Sent: Friday, October 10, 2008 12:42 PM
To: Luke Kucalaba
Cc: cmake@cmake.org
Subject: Re: [CMake] Running cmake multiple times to resolve cache
variables
Luke Kucalaba wrote:
I think the reason we need to run cmake.exe multiple times is because
we
typically have a main
PM
To: 'Bill Hoffman'
Cc: cmake@cmake.org
Subject: RE: [CMake] Running cmake multiple times to resolve cache
variables
Thanks Bill, I understand exactly what you are talking about. I looked
into our cmake project structure, and ran some tests. I think we
originally started out using a sequentially
