ARC Issue with Xcode 4.5.2 about plweakcompatibility HOT 5 CLOSED

I don't see this error here, building the project with Xcode 4.5.2. Are you including additional settings that trigger this?

from plweakcompatibility.

Here's the Xcode error

I used the highlighted suggestion to "fix" the issue. I don't believe we've got any settings out of the ordinary. Here's the linker flags:

We're compiling against iOS 6 SDK, with a Minimum target version of 4.3, using LLVM 4.1. It's failing to compile in our Debug build, which uses no compiler optimizations (whereas release builds use Fastest & Smallest -0s, and it also fails to compile there). The only C flags are the ones the documentation lists to convince Xcode to compile with weak enabled.

It is compiling the .m using ARC, although I don't see anything in the docs about that being an issue. The issue code never actually gets hit in our scenario because we're not using the Mazwr lib.

What other settings might be causing it would you think?

from plweakcompatibility.

I still can't make the error show up here. Maybe you have a prefix header that's getting in the way somehow? But it may not be necessary. While trying to figure out what was going on, I discovered that the internal prototype for -initWithTarget: was declared as a class method! Oops. This is now fixed in commit a9ec557. Pull that down and give it a try. If the error still happens, see what sort of stuff you have in your prefix header, as I suspect there's a conflicting prototype for that method somewhere.

from plweakcompatibility.

Pulled down the commit. That didn't fix it. Did a global search for initWithTarget and, sure enough, we've got some remnants of Three20 in our codebase included in the PCH, and one of those (TTURLNavigatorPattern) has a function
- (id)initWithTarget:(id)target

Commented that out, and sure enough everything built. Sounds like time for some internal house cleaning (I don't think we use that part of Three20 anymore as we've slowly been moving off it). Thanks for the point in the right direction, and happy to see we at least fixed something :)

from plweakcompatibility.

Cool, glad you got it worked out. You prompted some much-needed housekeeping on the project even if the problem was elsewhere, so that's good.

from plweakcompatibility.