qscintilla-qt5 @ 2.13.0_0: Could not resolve SDK Path for 'macosx10.11'

[thetrial (alabay)]

Interesting. The same problem as in #62940.

[thetrial (alabay)]

I investigated a bit further and found #62857.

I’m not quite sure if this is a hack or a solution, but in a slightly modified form I created an alias of MacOSX.sdk, namin it manually MacOSX10.12.sdk. The paths are a bit different:

/Library/Developer/CommandLineTools/SDKs
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs

Well, qscintilla-qt5 built now. But maybe not everyone wants to fiddle around in the data system.

[michaelld (Michael Dickens)]

I started looking into this once ... it's an issue with how Qt determines the SDK path. Can you report back what the following command returns:

/bin/ls -lAF $(xcode-select -p)/Platforms/MacOSX.platform/Developer/SDKs/

[michaelld (Michael Dickens)]

Thanks also for the update @thetrail. If we can gather some info on SDK naming then I think we can work out a reasonable solution.

[thetrial (alabay)]

At this moment I get this:

total 2448
drwxr-xr-x@ 5 user  staff      170 17 Sep  2017 MacOSX.sdk/
-rw-r--r--@ 1 user  staff  1246888  1 Okt 20:08 MacOSX10.11.sdk
lrwxr-xr-x  1 user  staff       10 18 Mär  2019 MacOSX10.12.sdk@ -> MacOSX.sdk

Well, this doesn’t look so fine to me, maybe I should not use the Finder to alias MacOSX.sdk, but the CLI to symlink. At the moment I try, if sqlitebrowser goes through. After that I’ll try to symlink instead alias the original directory.

[thetrial (alabay)]

Now I've changed that to:

drwxr-xr-x@ 5 user  staff  170 17 Sep  2017 MacOSX.sdk/
lrwxr-xr-x  1 user  staff   94  1 Okt 20:40 MacOSX10.11.sdk@ -> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
lrwxr-xr-x  1 user  staff   10 18 Mär  2019 MacOSX10.12.sdk@ -> MacOSX.sdk

Not sure, why the target once is a full path and once only the folder itself.

[thetrial (alabay)]

Oh, caveat. When using ln -s I get the error back again. It has to be done via Finder! So the last change is useless. I guess, this is only a hack.

[thetrial (alabay)]

With qscintilla-qt5 @2.13.3_0 the problem reocurred. Though I haven’t changed my setup.

I don’t see, what the problem is, so I’ll post the mainlog file.

[michaelld (Michael Dickens)]

@thetrial: in the Portfile for qscintilla-qt5, add in use_xcode yes ... I have it at line 28. Clean qscintilla-qt5 then try installing again. This works for me for qscintilla-qt5, py*-pyqt5, and py*-pyqt5-qscintilla. Hope it works for you too!

[thetrial (alabay)]

No, it did not work. The error stays the same :-(

[michaelld (Michael Dickens)]

@thetrail: Unless you've messed with the SDKs, adding in some extras and/or some links back and forth between the various installs, then adding in use_xcode yes should do the trick. The log shows the error associated with not using use_xcode yes, in my experience.

Related: it looks like your host OS is MacOSX 10.11.6. Someone correct me if I'm wrong, but I don't think it's wise to build for a future MacOSX (10.12) within an older MacOSX (10.11). Why do you have OSX 10.12 SDK installed? Strongly recommend you remove it & get the Xcode and CLT back to defaults.

[thetrial (alabay)]

I cleaned qscintilla-qt5, I wrote use_xcode yes into the portfile, I said sudo port install qscintilla-qt5 … and the error stays.

Regarding OS and SDK – I haven’t modified anything. This is the way it naturally goes. It’s not intended by me. And I’m also not so deep into it that I would build for a future OS. I installed macports, I have the system-related xcode, and I install my ports. Something is broken with this update now, and I don’t know what.

[michaelld (Michael Dickens)]

@thetrial : OK thanks for the update. Let me boot a device into MacOSX 10.11 & see what happens for me, what I see for SDK installs etc

[thetrial (alabay)]

Has something changed? Version 2.13.3 ran through today. Before that, lots of qt-related updates happened, so I’m not sure on what it depends, that the update ran through – but it did. Just to mention that here.

[mascguy (Christopher Nielsen)]

Replying to thetrial:

Has something changed? Version 2.13.3 ran through today. Before that, lots of qt-related updates happened, so I’m not sure on what it depends, that the update ran through – but it did. Just to mention that here.

This was resolved by the fix mentioned here: comment:23:issue:65293