Oh, have you tried the Legacy Build System? It is under your File menu in either Workspace Settings or Project Settings.

Check your build settings for the location of your precompiled header.

I’m sure you all know that you can right click on a test in Xcode, select Profile and then run that test in Instruments. Oddly, when I set my Test scheme to ask which test to launch or use

I found the issue in the end. For some reason, the configuration in one project was set at the project level, while it was at the target level in the other. When it is set at target level, definitions

Header maps doesn't appear to be the issue. It is the fact that no header search paths are specified for the prefix header, except for one target. Looking at the two targets in the same project, both

Hi all: I have the following properties in my Watch App Extension: @property (weak, nonatomic) IBOutlet WKInterfaceGroup *topGroup; @property (weak, nonatomic) IBOutlet WKInterfaceGroup

We use .xconfig files and have moved from XC9 through to XC11 and I haven't seen issues with settings in xcconfigs not being honoured. However, the big change between the old & new build systems, and

I have been working on changing a C/C++/Objective C app that uses the Nano library so that it uses the LLVM C++ Standard Library rather than the GNU version. After a fair bit of work in Xcode 9, I get

Thanks, Alex. My architectures build settings do match yours. This is an old project, originating in 2009. There are 7 targets, and this behavior is common to at least 2 of them. At least one of

Yeah, in build settings, what are your settings for Valid Architectures? Just enter Architectures in the search field in Build Settings and that should help. I’ve got these on one of my

Working on an iOS app, implemented in obj-C and C. I recently added a Cocoa touch class to the project, and the app builds and tests fine on iOS 12.2 simulators. However, when attempting to test on

Hi all, I’m having an involuntary adventure with the dynamic loader, as I attempt to link an ObjC code against anaconda python 3. (I worked out a solution for python 2.7 a while ago, but switching

I’m revising some iOS apps (for iOS 12.0) to use PDFView objects. I have included the PDFKit framework, but the IB objects library does not contain a PDFView. PDFKit programming guide is out of

with obj-c / c / c++ compiler i was able to force specific warnings into errors on a "per warning" basis. example, Xcode build console shows: "warning: unused variable 'i' [-Wunused-variable]" i then

*facepalm* That’s what I get for emailing on my iPad. Sorry! —Jens

You’re off a digit. Current Xcode is 10.2.1. Beta Xcode is 11.0. 12 is still in the future. Marc

Yes, it’s been out since WWDC a month ago. You can download beta 3 now; it’s pretty solid. —Jens

i tracked the difference down to this: "clang main.m -Werror -fobjc-arc" the "-fobjc-arc" is the one that causes the trouble. and we can't create modern apps without using arc these days. it looks

but when i build this exact source from terminal i am getting the warning (or error if warnings are treated as errors) as expected! > clang main.m -Werror > main.m:10:13: error: incompatible pointer

Yes. Re-read the example. If the function takes NSMutableDictionary**, it should complain when you pass it an NSDictionary**, same as if it wants NSMutableDictionary* and you pass it