I had this problem when I did a global replace of NSLog with DLog. I foolishly included the #define DLog(…) NSLog(… statements, so I ended up with #define DLog(…) DLog(… which caused the warnings, and a linker error.
You can choose the “Show the Assistant editor” view in the top right set of buttons in the toolbar. Then, at the top of the right-hand editor you can click the little Related Files button and then either choose Preprocess or Assembly. You can see an example of both the preprocessor output and generated assembly … Read more
Yes it is possible and I can assure you, the time savings are significant. When you compile your PCH, you have to copy the .pdb and .idb files from the project that is creating the PCH file. In my case, I have a simple two file project that is creating a PCH file. The header … Read more
You could try a deep clean (not the same as Product > Clean) – Option+Command+Shift+K Note: this means the clean the build folder (by pressing Option + Product -> clean folder)
Ewww… don’t put macros in a .pch file! A .pch file is, by definition, a project specific precompiled header. It really shouldn’t be used beyond the context of the project and it really shouldn’t contain anything but #includes and #imports. If you have some macros and such that you want to share between headers, then … Read more
Make new file: ⌘cmd+N iOS/Mac > Other > PCH File > YourProject-Prefix.pch. Make sure you display “All” and not “Basic”. (Blue buttons) Project > Build Settings > Search: “Prefix Header”. Under “Apple LLVM 7.0” you will get the Prefix Header key. Type file directory. e.g: “$(SRCROOT)/$(PROJECT_NAME)/ProjectName-Prefix.pch”. Clean project: ⌘cmd+⇧shift+K Build project: ⌘cmd+B
NOTE: Later versions of the IDE may use “pch” rather than “stdafx” in the default names for related files. It may be necessary to substitute pch for stdafx in the instructions below. I apologize. It’s not my fault. Right-click on your project in the Solution Explorer. Click Properties at the bottom of the drop-down menu. … Read more