On Fri, Sep 27, 2019 at 7:15 AM Chris Jones <[email protected]> wrote:
> > Odd. On my 10.13 machine it returns the versioned SDK. e.g. > > Titan ~/Projects/MacPorts/ports > xcrun --show-sdk-path > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk > Titan ~/Projects/MacPorts/ports > ls > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs > MacOSX.sdk MacOSX10.14.sdk > Titan ~/Projects/MacPorts/ports > ls -lth > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs > total 0 > drwxr-xr-x 7 root wheel 224B 30 Oct 2018 MacOSX.sdk > lrwxr-xr-x 1 root wheel 10B 17 Sep 2018 MacOSX10.14.sdk -> MacOSX.sdk > > ( so yes, Xcode 10 here also only has 'macOS release + 1' SDK ) > > what does > > ls -lth > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs > > > > give for you ? > > Chris > > total 0 lrwxr-xr-x 1 root wheel 10 Sep 24 13:59 MacOSX10.14.sdk -> MacOSX.sdk/ drwxr-xr-x 10 root wheel 320 Sep 24 13:58 MacOSX.sdk/ lrwxr-xr-x 1 root wheel 10 Sep 21 10:12 MacOSX10.15.sdk -> MacOSX.sdk/ drwxr-xr-x 4 root wheel 128 Aug 30 02:47 DriverKit19.0.sdk/ The MacOSX10.15.sdk symlink was created by the XCode 11 upgrade. The MacOSX10.14.sdk symlink was created by me to resolve some macports issues. I'm at my wits end with this. Is there some problem with the py36-pyqt5 port finding the correct sdk? On 27/09/2019 12:11 pm, Carlo Tambuatco wrote: > > On Fri, Sep 27, 2019 at 7:07 AM Chris Jones <[email protected] > > <mailto:[email protected]>> wrote: > > > > what does > > > > xcrun --show-sdk-path > > > > give you ? > > > > > > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk > > > > On 27/09/2019 12:04 pm, Carlo Tambuatco wrote: > > > I filed a ticket on this issue already and included a logfile for > > it, > > > but I thought there's no harm in asking the mailing list for a > quick > > > solution... > > > > > > I upgraded to macports 2.6.0 today. During a routine upgrade of my > > > ports, the py36-pyqt5 port failed to configure, possibly due to a > > > problem with the recent XCode 11 upgrade...? > > > > > > From logfile: > > > > > > Error: Failed to determine the detail of your Qt installation. > > Try again > > > using > > > the --verbose flag to see more detail about the problem. > > > Querying qmake about your Qt installation... > > > Determining the details of your Qt installation... > > > /opt/local/libexec/qt5/bin/qmake -o cfgtest_QtCore.mk > > cfgtest_QtCore.pro > > > Project ERROR: Could not resolve SDK Path for 'macosx10.14' using > > > --show-sdk-path > > > > > > > > > This is the first time something like this has happened. No > problems > > > before the XCode 11 upgrade. > > > > > > I upgraded to XCode 11 a few days ago, and as someone else > > pointed out, > > > XCode removed the MacOS10.14.sdk and replaced it with > MacOS10.15.sdk. > > > What I did to try and resolve it was create a MacOSX10.14.sdk > > symlink. > > > Is py36-pyqt5 one of those ports that has a hard-coded path to > > the 10.14 > > > SDK, and somehow isn't fooled by the symlink I created or > something? > > > > > > > > >
