DavidSpickett added a comment. If I run the test on 32 bit Arm I get these run lines:
: 'RUN: at line 4'; '/usr/bin/python3.8' /home/david.spickett/llvm-project/lldb/test/Shell/helper/build.py --compiler=any --arch=32 --tools-dir=/home/david.spickett/build-llvm-arm/./bin --libs-dir=/home/david.spickett/build-llvm-arm/./lib --objc-gnustep-dir="gnustep_install_dir-NOTFOUND" /home/david.spickett/llvm-project/lldb/test/Shell/Expr/objc-gnustep-print.m --compiler=clang --objc-gnustep --output=/home/david.spickett/build-llvm-arm/tools/lldb/test/Shell/Expr/Output/objc-gnustep-print.m.tmp Note the `NOTFOUND`. So cmake does set it to something, which means he feature is added, so the test is run but clearly it won't work. If you look around there are probably some examples of others handling this. Probably checking whether it's found, then assigning the path to some var. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D146058/new/ https://reviews.llvm.org/D146058 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
