xcrun error when building master

[gibfahn]

As of I think yesterday, when I run ./configure on macOS, I get a new xcrun error in addition to the xcodebuild warnings that we all know and love. The build still passes, but it'd be nice to avoid these.

Error:

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

xcrun: error: unable to lookup item 'PlatformPath' from command line tools installation
xcrun: error: unable to lookup item 'PlatformPath' in SDK '/'

• Version: master
• Platform: macOS
• Subsystem: build

[gibfahn]

Looks like change comes from: 3a334b1 which was #12450, so cc @refack.

[gibfahn]

The issue with the xcodebuild warnings is that on macOS you can have either the full Xcode, or just the command line tools (similar to the Visual Studio / Visual C++ build tools on Windows). The command line tools don't include xcodebuild, but gyp calls it and then never uses it so it's not actually a problem. I'm not sure if the xcrun is a similar problem, but looking at the commit diff, it looks like xcrun was already being called prior to this, it just wasn't giving errors.

[refack]

@gibfahn can you verify it's

tools/gyp/pylib/gyp/mac_tool.py:
79      -    args = ['xcrun', 'ibtool', '--errors', '--warnings', '--notices',
80      -        '--output-format', 'human-readable-text', '--compile', dest, source]
     86 +    args = ['xcrun', 'ibtool', '--errors', '--warnings', '--notices']

So I can dig deeper?

[refack]

(I meen that whole patched area )

[refack]

Is your os.environ['XCODE_VERSION_ACTUAL'] > '0700'?

[gibfahn]

I put some print statements in there but nothing happened. I don't know enough about GYP to know whether that file is even being triggered. I think it might not be.

I don't have any XCODE things in my environment (or os.environ) at all.

[refack]

Hmm. I'll have to spin up my hackintosh VM.
Which OSX ver you have? and version of the "Xcode Command Line Tools"?

[refack]

P.S. you say these errors comes from GYP (i.e. ./configure) not the ninja run, right?

[refack]

[not a solution]
P.P.S. have you tried https://github.com/nodejs/node-gyp? Mostly as an exercise...

1. rename /tools/gyp_node.py - to stop GYP from running
2. run ./configure to generate config.gypi
3. run gyp.js -Icommon.gypi -Iconfig.gypi [-Dtarget_arch=x64] node.gyp