2011/11/13 Robert Dailey :
> I understand that currently Makefiles generated by CMake are
> single-configuration by-design. In other words, you can't issue a "debug" or
> "release" command to make, you have to regenerate for a different
> configuration.
For this purpose you can use 2 build trees t
I'm trying to compile CMake using the MSVC toolchain but it isn't working
when I configure for the first time. The relevant output is below. What do
I need to do to get this working? I installed all the packages in Cygwin
with the word 'curl' in it, but it still isn't working:
-- Performing Curl T
Mateusz Loskot wrote:
I have a CMake-based project which builds several shared libraries and
executables.
There are various run-time dependencies between those shared libraries
and executables.
On Windows, I use Visual Studio for development, so I have
CMake-generated .sln with projects. loaded
I understand that currently Makefiles generated by CMake are
single-configuration by-design. In other words, you can't issue a "debug"
or "release" command to make, you have to regenerate for a different
configuration.
Can someone explain the reason for this design? Are there any plans to
change i
Moving forward, with new code, we should always use if(DEFINED) or
if(NOT DEFINED) constructs. They should largely be equivalent, except
for edge/corner cases you've noted involving variables whose values
are other variable names.
The construct found in lines such as:
IF("${VARIABLE}" MATCHES "^${
2011/11/13 Michael Hertling :
[...]
> Sorry, I talked nonsense in my previous reply. Obviously, the line
>
> IF("${VARIABLE}" MATCHES "^${VARIABLE}$")
>
> serves to prevent the macro's re-execution if the result variable is
> already defined, i.e. if the macro has most certainly been called
> befo
