[MacPorts] #65293: qmake5 PortGroup only works if use_xcode yes is applied to every PortFile that uses it: Project ERROR: Could not resolve SDK Path for 'macosx11' using --show-sdk-path

MacPorts noreply at macports.org
Sun Jun 5 18:55:40 UTC 2022


#65293: qmake5 PortGroup only works if use_xcode yes is applied to every PortFile
that uses it: Project ERROR: Could not resolve SDK Path for 'macosx11'
using --show-sdk-path
--------------------------+--------------------
  Reporter:  cooljeanius  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.7.2
Resolution:               |   Keywords:
      Port:  qtads        |
--------------------------+--------------------

Comment (by kencu):

 brief experiment on Monterey 12.4 with latest Xcode.

 Xcode installed in /Applications:
 {{{

 % /usr/bin/xcrun --sdk macosx12 --show-sdk-path
 2022-06-05 11:47:40.220 xcodebuild[40379:537785] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionSentinelHostApplications for extension
 Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in
 com.apple.dt.IDEWatchSupportCore
 2022-06-05 11:47:40.220 xcodebuild[40379:537785] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension
 Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of
 plug-in com.apple.dt.IDEWatchSupportCore
 xcodebuild: error: SDK "macosx12" cannot be located.
 2022-06-05 11:47:41.234 xcodebuild[40380:537802] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionSentinelHostApplications for extension
 Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in
 com.apple.dt.IDEWatchSupportCore
 2022-06-05 11:47:41.235 xcodebuild[40380:537802] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension
 Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of
 plug-in com.apple.dt.IDEWatchSupportCore
 xcodebuild: error: SDK "macosx12" cannot be located.
 xcrun: error: unable to lookup item 'Path' in SDK 'macosx12'

 % /usr/bin/xcrun --sdk macosx --show-sdk-path
 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk

 % /usr/bin/xcrun --sdk macosx12  --find ld
 2022-06-05 11:46:19.030 xcodebuild[40356:537066] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionSentinelHostApplications for extension
 Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in
 com.apple.dt.IDEWatchSupportCore
 2022-06-05 11:46:19.031 xcodebuild[40356:537066] Requested but did not
 find extension point with identifier
 Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension
 Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of
 plug-in com.apple.dt.IDEWatchSupportCore
 xcodebuild: error: SDK "macosx12" cannot be located.
 xcrun: error: sh -c
 '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk
 macosx12 -find ld 2> /dev/null' failed with exit code 16384: (null)
 (errno=No such file or directory)
 xcrun: error: unable to find utility "ld", not a developer tool or in PATH

 % /usr/bin/xcrun --sdk macosx  --find ld
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld

 }}}

 and with no Xcode installed in /Applications:
 {{{
 % /usr/bin/xcrun --sdk macosx12 --show-sdk-path
 xcrun: error: SDK "macosx12" cannot be located
 xcrun: error: SDK "macosx12" cannot be located
 xcrun: error: unable to lookup item 'Path' in SDK 'macosx12'

 % /usr/bin/xcrun --sdk macosx --show-sdk-path
 /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

 % /usr/bin/xcrun --sdk macosx12  --find ld
 xcrun: error: SDK "macosx12" cannot be located
 /Library/Developer/CommandLineTools/usr/bin/ld

 % /usr/bin/xcrun --sdk macosx  --find ld
 /Library/Developer/CommandLineTools/usr/bin/ld
 }}}

 So -- perhaps on systems > darwin19 (ie darwin 20+) we just always call
 {{{--sdk macosx}}} and skip the always-produces-an-error {{{--sdk
 macosx${configure.sdk_version} }}}? After all, as it seems we are not
 interested in getting into darwin12.1, darwin12.2, etc, this will always
 error out anyway.

 Maybe that would make the {{{use_xcode yes}}} no longer needed, somehow.

-- 
Ticket URL: <https://trac.macports.org/ticket/65293#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list