Enable ARC for a Single Objective‑C File in a Mixed‑Mode Xcode Project

Desired Outcome

Compile one Objective‑C source file with Automatic Reference Counting (ARC) while the rest of the project continues to use manual retain‑release memory management.

Prerequisites

• An Xcode project containing at least one .m file that you want to enable ARC for.
• Read/write access to the project directory.
• Xcode command‑line tools installed (for optional verification).

Procedure

1. Open the project in Xcode.
2. Select the target that contains the file.
3. Open the Build Phases tab and expand Compile Sources.
4. Locate the target file (e.g., MyViewController.m). Double‑click the Compiler Flags column for that row.
5. Enter -fobjc-arc and press Return. This adds the flag only for the selected translation unit.
6. Alternatively, open Build Settings, search for Other C Flags, click the + button to add a per‑file setting, choose the file, and set the value to -fobjc-arc.
7. Save the project and build (⌘B).

Expected Checks

• In the Build Settings view, the row for the file should show -fobjc-arc under Other C Flags; the project‑level CLANG_ENABLE_OBJC_ARC remains No for manual‑retain‑release files.
• To verify that the compiler inserted ARC calls, open Terminal, navigate to the project’s derived data folder, and run:

clang -fobjc-arc -S -o - MyViewController.m | grep -E 'objc_retain|objc_release|objc_autorelease'

You should see lines such as call void @objc_retain indicating the compiler emitted retain/release calls.

• Run the static analyzer: clang --analyze MyViewController.m and confirm no retain/release mismatch warnings.

Recovery Options

If the build fails or you observe unexpected behavior:

• Return to the Compile Sources list, delete the -fobjc-arc flag for the file, or set it to an empty string.
• Clean the build folder (⇧⌘K) and rebuild.
• If you suspect over‑release, enable zombies via Instruments → Zombies instrument to detect messages sent to deallocated instances.

Limitations

ARC only manages Objective‑C objects and Core Foundation types that are toll‑free bridged. For raw malloc/free or non‑bridged Core Foundation objects you must still call CFRelease or use the appropriate bridging casts (__bridge_retained, __bridge_transfer). Mixing ARC and manual code is safe only when ownership transfer annotations (__strong, __weak, __unsafe_unretained) are used correctly; otherwise you may see leaks or over‑releases.