<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>It's deprecated as of 14, and they're removing it if you JUST build for MacOS Deployment Target 15. If you set the deployment target to <15, you're good, otherwise you get this error:<br></div><div><br></div><div><b>error: 'CGDisplayCreateImageForRect' is unavailable: obsoleted in macOS 15.0 - Please use ScreenCaptureKit instead.</b><br></div><div><br></div><div>Caused by this in the SDK when compiling for deployment target 15.0:<br></div><div><b>@available(macOS, introduced: 10.6, deprecated: 14.4, obsoleted: 15.0, message: "Please use ScreenCaptureKit instead.")</b><br></div><div><br></div><div>There are other bugs all over, none I've brought up here, since most of them are Apple bugs, or are hard to tell if they are or not. But this one is a deliberate removal, so as soon as people install macOS 15 and try to compile with the latest SDK, anything with these APIs will error. I assume in some cases upstream will fix, but I wanted to put it out there that reports for these will be coming.<br></div><div><br></div><div>I'll create a proper ticket after release. Hell, I'll do one now, if people are ok with that, thanks to the relaxed NDA, but old habits die hard. <br></div><div><br></div><div>I'll take a look at these bugs you mention and file radars or whatever. If anyone is seeing bugs on a non-dev beta - I can file bugs if you reach out, I'm listed on the wiki as running the macOS 15 dev beta.<br></div><div><br></div><div>—Mark<br></div><div><br></div><div>P.S. - building qt-base with macos_deployment_target 14.0 does indeed fix things so, Thanks Ryan, because that worked great for me!<br></div><div><br></div><div>On Sun, Aug 25, 2024, at 10:57 PM, Fred Wright wrote:<br></div><blockquote type="cite" id="qt" style=""><div><br></div><div>On Thu, 15 Aug 2024, Mark E Anderson wrote:<br></div><div><br></div><div>> Just a heads up, `CGDisplayCreateImageForRect` is no longer supported in the macOS 15 SDK.<br></div><div><br></div><div>I don't know what SDK you're looking at, but I see that definition in the <br></div><div>macOS 15 SDK here, in both the beta 4 and beta 6 versions of XCode 16.<br></div><div><br></div><div>If that were really true, it's a bug that would need to be fixed before it <br></div><div>comes out of beta, since Apple encourages, and in some cases requires, <br></div><div>builds to use the SDK for the next later OS version than the one being <br></div><div>targeted. So the SDK for OS N+1 damn well better include all the <br></div><div>definitions for OS N.<br></div><div><br></div><div>There are at least two bugs that *do* exist in the macOS 15 SDK, at least <br></div><div>as of beta 6:<br></div><div><br></div><div>1) It still thinks it's a 14.0 SDK:<br></div><div>-------------------------------------------------------------------------<br></div><div>/*<br></div><div> * if max OS not specified, assume larger of (10.15, min)<br></div><div> */<br></div><div>#ifndef MAC_OS_X_VERSION_MAX_ALLOWED<br></div><div> #if MAC_OS_X_VERSION_MIN_REQUIRED > MAC_OS_VERSION_14_0<br></div><div> #define MAC_OS_X_VERSION_MAX_ALLOWED MAC_OS_X_VERSION_MIN_REQUIRED<br></div><div> #else<br></div><div> #define MAC_OS_X_VERSION_MAX_ALLOWED MAC_OS_VERSION_14_0<br></div><div> #endif<br></div><div>#endif<br></div><div>-------------------------------------------------------------------------<br></div><div>Note that the comment is even more outdated than the code. :-)<br></div><div><br></div><div>2) There are new functions for half-precision floats in 15.x, and their <br></div><div>prototypes are *unconditionally* included in math.h. That means that <br></div><div>building anything that uses math.h with a compiler that doesn't provide <br></div><div>the _Float16 type gets fatal errors. Availability attributes don't help <br></div><div>with this, since the declarations themselves are illegal without the type.<br></div><div>Usually, things of this form have conditionals related to compiler <br></div><div>capabilities, but that's currently missing here, and the usual "define it <br></div><div>as empty" approach doesn't work with types.<br></div><div><br></div><div>Anyone with a paid developer account should feel free to file bugs about <br></div><div>those. Those of us who don't pay Apple for the privilege of telling them <br></div><div>what they're doing wrong don't have that option.<br></div><div><br></div><div>On Fri, 16 Aug 2024, Mark E Anderson wrote:<br></div><div><br></div><div>> I do! I'll look into that. Yeah, I don't even have the 14 SDK on this machine since Xcode 15 won't run.<br></div><div><br></div><div>You don't need to *run* a version of Xcode just to extract an SDK from it. <br></div><div>Though in some cases you may trip over issues with the installer and/or <br></div><div>unarchiver.<br></div><div><br></div><div>Fred Wright<br></div><div><br></div></blockquote><div><br></div></body></html>