On 15 August 2011 20:23, Albert Meltzer buls...@gmail.com wrote:
Maybe the esteemed colleagues would suggest another good and reliable way
to handle situations such as this:
IF (lang STREQUAL perl) ...
ELSEIF(lang STREQUAL python) ...
ELSEIF()
...
ENDIF ()
without having to SET(perl
Thanks, Michael...
I'll give this another week or so here on the mailing list (and in the
bug tracker) to gather feedback.
If I don't hear anything else, I'll consider changing some
documentation to clarify the existing situation, but I don't see a
reasonable way to accommodate this feature
On Mon, Aug 15, 2011 at 11:26 AM, David Cole david.c...@kitware.com wrote:
Thanks, Michael...
I'll give this another week or so here on the mailing list (and in the
bug tracker) to gather feedback.
If I don't hear anything else, I'll consider changing some
documentation to clarify the
On Mon, Aug 15, 2011 at 3:26 PM, David Cole david.c...@kitware.com wrote:
documentation to clarify the existing situation, but I don't see a
reasonable way to accommodate this feature request *and* maintain
backwards compatibility with existing real world uses of macro and if
Umm... once
For most users, macros should be a taboo anyways. They are much better
served by functions, IMHO. In all of my projects I had only one case
where I actually needed a macro. That was when I wrapped a function
that set some variables in the PARENT_SCOPE and I had to propagate them
outside of the
Does anybody here on the list have an opinion one way or the other on
whether it's worth pursuing a fix to this re-opened bug regarding
CMake macro and if command behavior...?
Thanks for any input, either here on the list, or directly in the bug
notes themselves.
Thanks,
David
--
