> On 20 Sep 2018, at 3:54 am, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Sep 19, 2018, at 11:54, Richard L. Hamilton wrote: > >> So I think that the 10.13 SDK on Mojave, assuming one can still build >> against it there, may well be a short-term answer. > > Mojave requires Xcode 10 which contains only the 10.14 SDK. > > MacPorts doesn't have any particular support at this time for accessing > alternative SDKs that the user might have placed in other locations.
I am on High Sierra 10.13.6, but the App Store app told me to upgrade to Xcode 10 and command line tools 10 (on 19 Sept 2018), so I did. Now I am getting weird messages from ld when compiling and building some of my own C++ code which is based on KDE libraries obtained from Macports. Here is one example: ld: warning: text-based stub file /System/Library/Frameworks//ApplicationServices.framework/Versions/A/ApplicationServices.tbd and library file /System/Library/Frameworks//ApplicationServices.framework/Versions/A/ApplicationServices are out of sync. Falling back to library file for linking. There are other similar ones relating to CoreGraphics.framework, CoreText.framework, ImageIO.framework, CoreServices.framework and CFNetwork.framework. Also I am getting loads of compiler warning messages about mismatched ‘struct’ and ‘class’ keyword usages and loads of undefined ld symbols re the classes and methods affected. So the whole build fails. I had not edited, compiled or built that code since a few months ago. Have I gone an Xcode version or a compiler version too far? If so, what should I do? Cheers, Ian W. > I worked on a port to standardize a way to provide other SDK versions, but I > have not published it yet. MacPorts base changes would also be required to > make it easy for ports to request SDKs that didn't come from the primary > Xcode installation. > > >> But IMO, this is still a good excuse to at least get STARTED on pushing >> everything toward x86_64, even if workarounds are still mostly possible; >> because in the next OS version, i386 will likely be gone or severely >> crippled. > > Apple has announced that macOS 10.15 will remove all 32-bit support. > >
