Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6729159
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T10:15:22+00:00 2026-05-26T10:15:22+00:00

Since Xcode 4.2 comes with LLVM 3.0 we’re finally able to use automatic synthesizeation

  • 0

Since Xcode 4.2 comes with LLVM 3.0 we’re finally able to use automatic synthesizeation. You can turn it on by adding the following two flags to your Other C Flags in the Apple LLVM compiler 3.0 - Language section:

  • -Xclang
  • -fobjc-default-synthesize-properties

Now you can get rid of your @synthesize boiler plate code if you just want the default settings for your property synthesizeation (I guess we already use automatic reference counting).

When I hit build, the compiler warns me about missing @synthesize etc. statements, like so:

MyController.h:34:43: warning: property 'myProperty' requires method 'myProperty' to be defined - use @synthesize, @dynamic or provide a method implementation [3]
@property (strong, nonatomic) MyClass *myProperty;

I prefer a warning-free build, so the question is: How can I suppress this kind of warnings because obviously they don’t make sense anymore.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T10:15:22+00:00Added an answer on May 26, 2026 at 10:15 am

    Are you sure -Xclang is passed to the compiler

    clang -x objective-c -Xclang -fobjc-default-synthesize-properties -c TestClass.m -o TestClass.o 
    

    does not show any warnings while

    clang -x objective-c -fobjc-default-synthesize-properties -c TestClass.m -o TestClass.o
    

    does which is by the way correct since no properties are synthesized

    Here is the TestClass.m I used:

    #import <Foundation/Foundation.h>
    
    @interface TestClass : NSObject
    
    @property (nonatomic, strong) NSObject * test;
    
    @end
    
    @implementation TestClass
    
    @end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

since I updated to xcode 4.2 and iOS 5 following code has no effect:
Since upgrading to the latest Xcode 3.2.1 and Snow Leopard, I've been getting the
Since the keyboard is the interface we use to the computer, I've always thought
I've recently downloaded Xcode 4 and now two of my projects that were working
I have an iPhone project (Xcode, Objective C++) with two targets - A and
Since new Xcode 3.2 I find it very hard to add Quartz Core Framework.
Since upgrading to Xcode 3.2.1, I've experienced a strange issue that has really killed
Since I updated XCode for the new iOS 5.0 i get a warning in
I have been using XCode for IPhone development since start. Out of curiosity, are
I have some problems adding my shader-glsl files from one xcode project to another.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.