Opened 8 months ago

Last modified 2 weeks ago

#64927 assigned defect

qwt-qt5 @6.1.6_0: Could not resolve SDK path for 'macosx 12' using --show-sdk-path

Reported by: jcannon-gplates (John Cannon) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: arm64 monterey Cc: chrstphrchvz (Christopher Chavez), wrohv
Port: qwt-qt5


Configure phase fails with:

xcrun: error: SDK "macosx12" cannot be located

...and opening ".../qwt-qt5/main.log" shows:

Could not resolve SDK path for 'macosx 12' using --show-sdk-path

Adding the change from to the Portfile appears to fix it:

if { ${xcodeversion} ne "none" } {
    use_xcode       yes

...and despite now getting the following error message it still configures and builds/installs:

xcodebuild: error: SDK "macosx12" cannot be located

Note that I'm using buildfromsource always in macports.conf (and macosx_deployment_target 11.0). And building on Monterey on M1 using XCode 13.3.

Change History (5)

comment:1 Changed 8 months ago by chrstphrchvz (Christopher Chavez)

Cc: chrstphrchvz added

comment:2 Changed 5 weeks ago by wrohv

Experiencing this also on Ventura / XCode 14.1 / arm64. SDK "macosx13" cannot be located. The proposed patch resolves the issue for me as well.

comment:3 Changed 5 weeks ago by wrohv

Cc: wrohv added

comment:4 Changed 2 weeks ago by lavalleet (Tommy Lavallee)

fails with report message: Failed to configure qwt-qt5: configure failure: command execution failed

the main.log shows: Could not resolve SDK Path for 'macosx13' using --show-sdk-path

executing: xcrun --show-sdk-path results in the correct path shown below. /Applications/

however the log reports... :info:configure Project ERROR: Could not resolve SDK Path for 'macosx13' using --show-sdk-path

Note that the folder also contains MacOSX13.0.sdk and MacOSX13.sdk links to the MacOSX.sdk.

Using/Running the release MacOS Ventura 13.0 /Xcode 14.4 / arm64

I am available to support/provide more information as requested.

comment:5 Changed 2 weeks ago by kencu (Ken)

the code in the qmake5 PortGroup that manages this has recently been updated with many new debugging messages to help sort out folks like you.


I don't see these debugging messages in your report here, so I think perhaps your ports might need updating?

Try cleaning qwt-qt5, then update your ports tree, and then try again.

If it fails again, there should be a lot more debugging information we can use to see what happened.

You would have to post up the log for us to see them, or try to build in debug mode (-d) and you'll see them in the terminal.

Last edited 2 weeks ago by kencu (Ken) (previous) (diff)
Note: See TracTickets for help on using tickets.