3 ms·
Well, if you build your software the Apple way(TM) and use Xcode, just opening the project will show you all the deprecation warning. A C++ Xcode project I have
by Cycl0p 3y ago
Well, if you build your software the Apple way(TM) and use Xcode, just opening the project will show you all the deprecation warning. A C++ Xcode project I have at work has a lot of them, mainly for using old Frameworks like CoreServices, which do not have any modern C/C++ equivalent (they were replaced by Obj-C/Swift APIs) and which, while very old fashion/unsafe in their style, are most of the time way more worth to call for very short task like getting a path, rather then having to whip out a .mm and write some horrible Objective-C++.
However, if you’re not using Swift/Obj-C and have a different/custom build system, you’re probably toasted. Although, if you’re using CMake, you might have some luck in getting these info by generating an XCode project.
- Someone 3y agoI would expect Xcode doesn’t have its own parser, but gets its warnings from the compiler. It, in turn, would get them from the header files. If so, the problem wouldn’t be “not using Swift/Objective-C” or “have a different/custom custom build system”, but having a binary in your build that calls a deprecated API that the build does not build from source. That’s the case if you use a third party library you don’t have source code for, or if you use an in-house ‘library’ project (Xcode would warn you if you compiled that, but possibly not when you use it in another project, so you wouldn’t get a direct clue “rebuild that library to see the issues”).