ExternalProject: Don't treat YES as a keyword

This ultimately won't change behavior, since YES should never be listed
in the "keywords" argument. The original code looks like a bug though,
since YES satisfies the criteria for being interpreted as a keyword, and
there is logic to short-circuit on TRUE and FALSE. Add YES to that
condition to avoid any potential confusion.
This commit is contained in:
Craig Scott
2024-05-04 09:49:58 +10:00
parent a1743ce1ef
commit 91e1015722

View File

@@ -1341,7 +1341,7 @@ function(_ep_parse_arguments
if(arg MATCHES "^[A-Z][A-Z0-9_][A-Z0-9_]+$" AND
NOT (("x${arg}x" STREQUAL "x${key}x") AND
("x${key}x" STREQUAL "xCOMMANDx")) AND
NOT arg MATCHES "^(TRUE|FALSE)$")
NOT arg MATCHES "^(TRUE|FALSE|YES)$")
if(arg IN_LIST keywords)
set(is_value 0)
endif()