srch

if(DEFINED <name>|CACHE{<name>}|ENV{<name>}). True if a variable, cache variable or environment variable with given <name> is defined. The value of the variable does ...

... string(COMPARE EQUAL "CMake" "CMake" ceqvar) 75 string(COMPARE NOTEQUAL "CMake" "Autoconf" cneqvar) 76 string(COMPARE NOTEQUAL "CMake" "CMake" ncneqvar) ...

True if the given string or variable's value is lexicographically greater than the string or variable on the right. if(<variable|string> STREQUAL <variable| ...

because there can be an unintended double expansion of the first argument if the variable A happens to be defined to a string which is also the name of a CMake variable, e.g.: set (A "d") set (d "some string") if ("$ {A}" STREQUAL "some string") # this branch will be taken message ("oops...") else () message ("fine") endif ()

[CMake] Case-insensitive string compare. David Cole david.cole at kitware.com. Thu Jun 7 18:51:36 EDT 2012. Previous message: [CMake] Case-insensitive ...

Feb 08, 2011 · matches - cmake string not equal CMake compare to empty string with STREQUAL failed (1) I always think that if you want to compare two strings (but not variables) all you need to do is to quote it like that:

Cmake commands do not see these quotes. Therefore, STREQUAL can never know the difference between "baz" and baz. So, STREQUAL treats a parameter as a variable name if it is defined, but as a string value if it is not. (I verified this in cmIfCommand.cxx) Is this quote behavior well-known among cmake users? For others like me,

Compare the two JSON objects given by <json-string1> and <json-string2> for equality. The contents of <json-string1> and <json-string2> should be valid JSON. The <out-var> will be set to a true value if the JSON objects are considered equal, or a false value otherwise.

Turning my comment into an answer. Concatenating a list would simply be achieved by putting quotes around the variable reference:

True if the given string or variable's value is lexicographically equal to the string or variable on the right. ... The if command was written very early in CMake's ...

[CMake] Case-insensitive string compare. Robert Dailey. 10 years ago. Permalink. How can I perform a case-insensitive string comparison? I basically need to

COMPARE EQUAL/NOTEQUAL/LESS/GREATER will compare the strings and store true or false in the output variable. ASCII will convert all numbers into ...

I'm starting to convert our scripts to use this hopefully foolproof > > alternative: > > > > string(COMPARE EQUAL "${build_system}" windows ...

Search and Replace string(FIND <string> <substring> <out-var> [. ... <value>) string(JSON <out-var> [ERROR_VARIABLE <error-var>] EQUAL <json-string1> ...

I'm starting to convert our scripts to use this hopefully foolproof alternative: string(COMPARE EQUAL "${build_system}" windows _cmp) if ...

Write a string representation of the current date and/or time to the <output_variable>. If the command is unable to obtain a timestamp, the <output_variable> will be set to the empty string "". The optional UTC flag requests the current date/time representation to be in Coordinated Universal Time (UTC) rather than local time.

Feb 14, 2013 · Cmake commands do not see these >> quotes. Therefore, STREQUAL can never know the difference between "baz" >> and >> baz. >> >> So, STREQUAL treats a parameter as a variable name if it is defined, but >> as >> a string value if it is not. (I verified this in cmIfCommand.cxx) >> >> Is this quote behavior well

treated as strings. Then I learned that the interpreter is the only one that sees quotes around parameters, for the sole purpose of string interpolation and preventing whitespace from splitting a parameter. Cmake commands do not see these quotes. Therefore, STREQUAL can never know the difference between "baz" and baz.

You ran into a rather annoying "it's not a bug, it's a feature" behavior of CMake. As explained in the documentation of the if command:. The if command was written very early in CMake's history, predating the ${} variable evaluation syntax, and for convenience evaluates variables named by its arguments as shown in the above signatures.

[CMake] set(a b); set(b c); if(a STREQUAL b OR a STREQUAL c) . ... com/questions/19982340/cmake-compare-to-empty-string-with-strequal-failed ...

And then this still tells me "test" is not the empty string. Which can be considered expected behaviour if an empty variable is not the empty string, but both are "NOT test".