summaryrefslogtreecommitdiffstats
path: root/Source/cmIfCommand.cxx
Commit message (Collapse)AuthorAgeFilesLines
* If: Introduce policy CMP0054 - don't dereference quoted variables in if()Nils Gladitz2014-09-111-5/+5
|
* If: Extract cmConditionEvaluator from if() implementationNils Gladitz2014-09-111-701/+12
|
* ClearMatches: Only clear matches which were actually setBen Boeckel2014-04-291-2/+2
| | | | | | | ClearMatches was clearing many variables which were never set in the first place. Instead, store how many matches were made last time and only clear those. It is moved to the cmMakefile class since it is a common utility used by multiple commands.
* Remove some c_str() calls.Stephen Kelly2014-03-111-6/+6
| | | | | | Use the clang RemoveCStrCalls tool to automatically migrate the code. This was only run on linux, so does not have any positive or negative effect on other platforms.
* stringapi: Use strings for variable namesBen Boeckel2014-03-081-9/+9
| | | | Variable names are always generated by CMake and should never be NULL.
* cmMakefile: make some methods take const std::string& instead of const char*Rolf Eike Beer2014-01-161-1/+1
| | | | | | | | Most callers already have a std::string, on which they called c_str() to pass it into these methods, which internally converted it back to std::string. Pass a std::string directly to these methods now, avoiding all these conversions. Those methods that only pass in a const char* will get the conversion to std::string now only once.
* De-duplicate version comparison code.Stephen Kelly2013-06-121-36/+4
| | | | | Extend the VersionCompare in cmSystemTools to handle 8 components, and port the if command to use that.
* if: Compare up to 8 components in VERSION testsBrad King2012-09-111-6/+10
| | | | | | | | | | Extend the number of components tested by if(... VERSION_LESS ...) if(... VERSION_EQUAL ...) if(... VERSION_GREATER ...) from 4 to 8. The latter is a more extreme maximum.
* Print any evaluated 'elseif'/'else' commands in trace mode (#13220)Brian Helba2012-05-161-0/+13
| | | | | | In trace mode ('--trace'), any 'elseif' or 'else' commands that are evaluated as part of a conditional block will be printed. Previously, only the opening 'if' command of a conditional block was printed.
* fix uninitialized var in if(NOT foo bar STREQUAL "foo bar")Rolf Eike Beer2012-01-221-0/+1
| | | | Also adds test to verify this.
* Remove unreachable code in cmIfCommandBrad King2009-10-281-1/+0
| | | | | The commit "Fix if() command and CMP0012 OLD/NEW behavior" introduced an unreachable 'break' after 'return' in a switch statement. We remove it.
* Fix if() command and CMP0012 OLD/NEW behaviorBrad King2009-10-271-73/+93
| | | | | | | | | | | | | | The commit "modified the if command to address bug 9123 some" changed the if() command behavior with respect to named boolean constants. It introduced policy CMP0012 to provide compatibility. However, it also changed behavior with respect to numbers (like '2') but did not cover the change with the policy. Also, the behavior it created for numbers is confusing ('2' is false). This commit teaches if() to recognize numbers again, and treats them like the C language does in terms of boolean conversion. We also fix the CMP0012 check to trigger in all cases where the result of boolean coersion differs from that produced by CMake 2.6.4.
* Report expanded arguments in if() command errorsBrad King2009-10-271-20/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The if() command reports its arguments at the beginning of some error messages. Originally it reported the un-expanded form of the arguments because in ancient CMake versions no context information was available. Now it is more useful to see the real arguments, which may be mentioned in the main error message. Since full context information is now available, users can refer back to the source if they need to see the unexpanded form of the arguments. For example, the code set(regex "++") if("x" MATCHES "${regex}") endif() now produces the message if given arguments: "x" "MATCHES" "++" Regular expression "++" cannot compile instead of if given arguments "x" MATCHES "${regex}" Regular expression "++" cannot compile
* Add IS_SYMLINK test to if commandBrad King2009-10-211-0/+7
|
* Clarify documentation and message for CMP0012Brad King2009-10-021-6/+4
| | | | | | | This commit re-words the warning message produced for CMP0012 to avoid the word 'you' since often the person reading the message is not the author of the code. We also add an example of the bad OLD behavior to the policy documentation.
* Convert CMake to OSI-approved BSD LicenseBrad King2009-09-281-14/+9
| | | | | | | This converts the CMake license to a pure 3-clause OSI-approved BSD License. We drop the previous license clause requiring modified versions to be plainly marked. We also update the CMake copyright to cover the full development time range.
* ENH: Improve format of if() command messagesBrad King2009-06-171-6/+4
| | | | | | | Errors and warnings from the if() command always display the argument list given to the command followed by an explanation of the problem. This moves the argument list into a pre-formatted block and follows it with a paragraph-form explanation. The result looks cleaner.
* ENH: warning fixKen Martin2009-06-121-4/+4
|
* ENH: modified the if command to address bug 9123 someKen Martin2009-06-121-111/+233
|
* ENH: Better handling of mismatched blocksBrad King2009-01-211-1/+2
| | | | | | | | | | | | | | | | If a logical block terminates with mismatching arguments we previously failed to remove the function blocker but replayed the commands anyway, which led to cases in which we failed to report the mismatch (return shortly after the ending command). The recent refactoring of function blocker deletion changed this behavior to produce an error on the ending line by not blocking the command. Furthermore, the function blocker would stay in place and complain at the end of every equal-level block of the same type. This teaches CMake to treat the begin/end commands (if/endif, etc.) as correct and just warns when the arguments mismatch. The change allows cases in which CMake 2.6.2 silently ignored a mismatch to run as before but with a warning.
* ENH: Better error message for unclosed blocksBrad King2009-01-211-18/+0
| | | | | | This centralizes construction of the error message for an unclosed logical block (if, foreach, etc.). We record the line at which each block is opened so it can be reported in the error message.
* ENH: Refactor function blocker deletionBrad King2009-01-201-12/+4
| | | | | | | | | When a function blocker decides to remove itself we previously removed it at every return point from the C++ scope in which its removal is needed. This teaches function blockers to transfer ownership of themselves from cmMakefile to an automatic variable for deletion on return. Since this removes blockers before they replay their commands, we no longer need to avoid running blockers on their own commands.
* ENH: Improve response to bad if or elseifBrad King2009-01-201-2/+9
| | | | | | | Previously bad arguments to an if() or elseif() would cause some subsequent statements in the corresponding block to execute. This teaches CMake to stop processing commands with a fatal error. It also provides context to bad elseif() error messages.
* STYLE: fix line length stuff for KWStyleBill Hoffman2008-10-011-1/+2
|
* ENH: Add version comparison to if() commandBrad King2008-09-101-0/+48
| | | | | | Provide VERSION_LESS, VERSION_EQUAL, and VERSION_GREATER operators in the if() command. This simplifies component-wise comparison of version numbers in the form "major[.minor[.patch[.tweak]]]".
* ENH: Add if(TARGET) commandBrad King2008-08-201-0/+7
| | | | | | | | | | It is useful to be able to test if a target has been created. Often targets are created only inside conditions. Rather than storing the result of the condition manually for testing by other parts of the project, it is much easier for the other parts to just test for the target's existence. This will also be useful when find-modules start reporting results with IMPORTED targets and projects want to test if a certain target is available.
* BUG: fix memory leak and cleanup error string codeKen Martin2008-06-281-31/+21
|
* ENH: support parenthesis as arguments and in conditionals feature request #6191Ken Martin2008-06-261-222/+277
|
* ENH: Add "if(POLICY policy-id)" option for IF command.Brad King2008-03-201-0/+17
| | | | | | | | | | | - This will help projects support multiple CMake versions. - In order to set a policy when using a newer CMake but still working with an older CMake one may write if(POLICY CMP1234) cmake_policy(SET CMP1234 NEW) endif(POLICY CMP1234) - Note that since CMake 2.4 does not have if(POLICY) supporting it will also require using "if(COMMAND cmake_policy)"
* ENH: fix warningsBill Hoffman2008-03-011-1/+1
|
* ENH: make CMAKE_ALLOW_LOOSE_LOOP_CONSTRUCTS the default and remove the ↵Bill Hoffman2008-02-291-3/+4
| | | | property. If any value is specified in an endif, endforeach, endwhile, etc then make sure it matches the start string. If no values are given then it is no longer an error.
* ENH: add return and break support to cmake, also change basic command ↵Ken Martin2008-01-231-64/+99
| | | | invocation signature to be able to return extra informaiton via the cmExecutionStatus class
* BUG: this seems to fix the regexp result-storage problem, now it seems the ↵Alexander Neundorf2007-08-291-1/+1
| | | | | | actual result is tored instead of "1" , as it happened for StringFileTest on Windows Alex
* ENH: also store the group matches from IF( MATCHES) in CMAKE_MATCH_(0..9)Alexander Neundorf2007-08-291-1/+5
| | | | Alex
* ENH: add IF(IS_ABSOLUTE path), so no regex matching is required in the cmake ↵Alexander Neundorf2007-06-061-0/+16
| | | | | | scripts Alex
* BUG: All variable accesses should produce watch callbacks, including ↵Brad King2007-05-171-3/+4
| | | | IF(DEFINED <var>) ones. Instead we define a new access type for IF(DEFINED) so that the error does not show up for backward compatibility variables.
* BUG: Do not complain about missing watched variables when they are accessd ↵Brad King2007-05-171-1/+1
| | | | with IF(DEFINED VAR).
* ENH: fix a warning and a nice fix to the IF commandKen Martin2006-12-121-4/+18
|
* ENH: make properties a bit more formal with documentation and chainingKen Martin2006-12-071-1/+2
|
* ENH: remove old hack now that project level compatibility files are supportedKen Martin2006-11-161-17/+0
|
* BUG: It cannot be an error if the values do not convert. The docs say that ↵Brad King2006-10-251-17/+4
| | | | if the values do not convert the test is false.
* BUG: For LESS, GREATER, and EQUAL check that the arguments can actually be ↵Brad King2006-10-251-3/+23
| | | | converted to numbers. Also force the conversion results to be stored in memory to make sure they both use the same precision. This addresses bug#3966.
* ENH: Remove old IF(FILE_IS_NEWER) syntax. It was never in a release anyway.Brad King2006-10-231-23/+0
|
* ENH: Patch from Alex to provide nicer syntax for FILE_IS_NEWER. Using name ↵Brad King2006-10-231-0/+23
| | | | IS_NEWER_THAN so old syntax will continue to work.
* ENH: added elseifKen Martin2006-09-221-9/+56
|
* STYLE: Fixed line-too-long.Brad King2006-08-261-3/+5
|
* ENH: Patch from Alex for adding IF(FILE_IS_NEWER). I also added a test.Brad King2006-08-251-1/+22
|
* ENH: reduce string construct delete opsKen Martin2006-05-311-5/+5
|
* COMP: fix warningKen Martin2006-05-191-2/+0
|
* ENH: allow loose loop constructsKen Martin2006-05-181-32/+13
|
generated by cgit v0.12 at 2024-12-28 03:45:48 (GMT)