summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-05-14 08:18:06 +0000
committerPavel Labath <pavel@labath.sk>2019-05-14 08:18:06 +0000
commit56f9afaf6b16eacdd497105ef2b34353c269fd83 (patch)
tree718f54c4ab80d9b4088a6878af7d2b364a742646 /lldb/packages/Python/lldbsuite/test/python_api/thread
parentc5c9ca0ba1bf508588c3ed0d871c43cfcbb07cd8 (diff)
downloadbcm5719-llvm-56f9afaf6b16eacdd497105ef2b34353c269fd83.tar.gz
bcm5719-llvm-56f9afaf6b16eacdd497105ef2b34353c269fd83.zip
[CMake] Correctly reinstate LLDB_CAN_USE_LLDB_SERVER
r360631 introduced a "syntax error" which meant that cmake was still not honoring the value of LLDB_CAN_USE_LLDB_SERVER variable. The correct syntax for seting an internal cache variable is "set(VAR value CACHE INTERNAL)", but the patch omitted the "CACHE" keyword. The "syntax error" is in quotes because without the CACHE keyword this is still valid syntax for setting the value of LLDB_CAN_USE_LLDB_SERVER to "1 INTERNAL". There doesn't seem to be a need for this to be a cache variable so I'm reverting this variable to a plain one, as it was before r360621. This will hopefully fix the windows build. llvm-svn: 360652
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud