Gibson Fahnestock

I have both command line tools and full xcode installed (I think), but I've `xcode-select`ed the Command Line Tools as my main one.

```bash ▶▶▶ xcode-select -p ~/wrk/com/node (f76ce0a756) /Library/Developer/CommandLineTools ``` Does llnode require the full version of Xcode? I was hoping to just use the command line tools.

Then I'm back to being confused about how llnode is "unable to locate lldb binary" if there's one in the path.

I had a chat with @hhellyer about this, and we came to the conclusion that: If you have `lldb` installed, but not `xcodebuild` or `llvm-config`, then you're probably using the...

https://github.com/nodejs/llnode#quick-start I thought there was a script that was installed that wrappers lldb with the plugin install. https://github.com/nodejs/llnode/blob/efaf0234bffc2cfe4871c6f15b2e14e7c5c7607f/package.json#L10 https://github.com/nodejs/llnode/blob/efaf0234bffc2cfe4871c6f15b2e14e7c5c7607f/scripts/configure.js#L142

@joyeecheung does that error if the plugin isn't installed?

I meant the `lldbinit` approach. So it prints an error but otherwise works fine? I was thinking of adding it to my dotfiles 😁 .

I'm torn, I like the simplicity of Choo (and I assume we're unlikely to need something complex). However I agree that the average contributor is likely to be more familiar...

Doesn't seem to work for me on macOS with the latest npm version of `node-core-utils`, am I doing something wrong? ``` git version: 2.16.2 node-core-utils version: 1.11.1 ```

Happy to raise a PR for this.