Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CMakeTools on my mac machine doesn't find any kits.

See original GitHub issue

Brief Issue Summary

CMakeTools on my mac machine doesn’t find any kits.

When I scan for kits nothing shows up, nor do I get any error messages in the UI.

But I do find some clues in the Developer Tools console where it says the GCC and Clang binaries are “bad”. But I don’t understand why they are deemed as such.

Expected:

I have XCode 11 installed with Command Line Tools. I was expecting CMakeTools to find the installed tools as described in the docs: https://vector-of-bool.github.io/docs/vscode-cmake-tools/kits.html

Developer Tools Log

[Extension Host] [CMakeTools] 2019-10-07T19:00:15.589Z [debug] [kit] Scanning for Kits on system
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.590Z [debug] [kit] Scanning directory /Users/thomas/.rvm/gems/ruby-2.5.3/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.591Z [debug] [kit] Scanning directory /Users/thomas/.rvm/rubies/ruby-2.5.3/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.592Z [debug] [kit] Scanning directory /Users/thomas/.rvm/gems/ruby-2.5.3@global/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.592Z [debug] [kit] Scanning directory /usr/local/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.593Z [debug] [kit] Scanning directory /usr/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.593Z [debug] [kit] Scanning directory /bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.594Z [debug] [kit] Scanning directory /usr/sbin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.595Z [debug] [kit] Scanning directory /sbin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.595Z [debug] [kit] Scanning directory /Users/thomas/.rvm/bin for compilers
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.597Z [debug] [kit] Found 0 kits in directory /Users/thomas/.rvm/gems/ruby-2.5.3/bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.599Z [debug] [kit] Found 0 kits in directory /Users/thomas/.rvm/rubies/ruby-2.5.3/bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.601Z [debug] [kit] Found 0 kits in directory /Users/thomas/.rvm/gems/ruby-2.5.3@global/bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.615Z [debug] [kit] Found 0 kits in directory /usr/local/bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.617Z [debug] [kit] Found 0 kits in directory /bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.628Z [debug] [kit] Found 0 kits in directory /usr/sbin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.631Z [debug] [kit] Found 0 kits in directory /sbin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.631Z [debug] [kit] Found 0 kits in directory /Users/thomas/.rvm/bin
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.641Z [debug] [kit] Testing Clang-ish binary: /usr/bin/clang
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.642Z [debug] [kit] Testing Clang-ish binary: /usr/bin/clang
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.656Z [debug] [kit] Testing GCC-ish binary: /usr/bin/gcc
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.675Z [debug] [kit] Testing GCC-ish binary: /usr/bin/llvm-gcc
console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.712Z [debug] [kit] Bad GCC binary /usr/bin/llvm-gcc -v output: Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.712Z [debug] [kit] Bad GCC binary /usr/bin/gcc -v output: Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

console.ts:137 [Extension Host] [CMakeTools] 2019-10-07T19:00:15.713Z [debug] [kit] Bad Clang binary /usr/bin/clang -v output: Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Platform and Versions

Operating System: macOS 10.14.6
CMake Version: 3.15.4
VSCode Version: 1.38.1
CMake Tools Extension Version: 1.1.3
Compiler/Toolchain: XCode 11 (11A420a)

Other Notes/Information

Available binaries in /usr/bin/:

clang
clang++
gcc
g++

All binaries report back their versions when I invoke them from the terminal with -v.

/usr/bin is present in PATH.

Issue Analytics

State:
Created 4 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

bobbrowcommented, Oct 7, 2019

It seems that Apple changed their version output string and the extension was checking for it. I’ll fix it.

1reaction

bobbrowcommented, Nov 5, 2019

CMake Tools 1.2.0 is available in the VS Code Marketplace or on the Releases Page

Because the publisher id has changed, VS Code does not automatically upgrade you yet. The Marketplace team will enable this in the next few days. If you want to install 1.2.0 now, please make sure you uninstall any earlier versions of CMake Tools manually to avoid any conflicts.

Top Results From Across the Web

Visual Studio Code CMake Tools ignores custom kits?

The documentation says I can define kits in .vscode/cmake-kits.json . I create this file and add this: [ { "name": "Clang 15.0.1", ...

Get started with CMake Tools on Linux - Visual Studio Code

Open the Command Palette (Ctrl+Shift+P) and run CMake: Select a Kit. The extension will automatically scan for kits on your computer and create ......

Cmake tools Visual studio code cannot find kits - YouTube

The problem happen when the file " cmake - tools - kits.json" in folder C:\Users\&{YOURNAME}\AppData\Local\CMakeTools\ has wrong json form0:00 ...

vscode-cmake-tools/support - Gitter

Hi guys! I would like to ask if anyone of you has experienced issues with the CMakeTools extension to VScode when the Cmake...

Cross Platform Make - CMake

If not supplied, CPack will create a file with some name based on ... On Mac OS X, installers that download components on-the-fly...