iOS编译资源前如何提前下载第三方库？已尝试Run Script等方法无效

Hey there, let's dig into why your script isn't triggering when you expect it to, and walk through actionable fixes to get it working reliably.

1. Fix Your Run Script Phase Configuration (Most Likely Culprit) #

You mentioned adding a Run Script Phase before "Compile Sources"—but there are a few easy-to-miss settings that might be making Xcode skip it:

• Uncheck "Run script only when installing": This box is often accidentally enabled, which restricts the script to run only during archive or install workflows, not regular development builds.
• Add Input/Output Files to Force Execution: Xcode skips scripts if it detects no changes to relevant files. Define the library file your script produces as an Output File (and any trigger files like a version check file as Input Files) so Xcode knows to run the script if the output is missing or outdated.
  • Example: If your script downloads the library to $(SRCROOT)/ThirdParty/MyLibrary.framework, add that exact path to the Output Files section.
• Verify script path and working directory: Use $(SRCROOT) to reference your project's root directory, ensuring your script path is correct. For example:

  python3 $(SRCROOT)/scripts/download_library.py
  

• Lock in the phase order: Drag the Run Script Phase to be the very first entry in your target's Build Phases—before even "Link Binary With Libraries" (though placing it right before "Compile Sources" is non-negotiable).

2. Use Scheme-level Build Pre-Actions #

If target-level pre-build actions aren't working, try setting up a pre-action in your scheme—this runs once before the entire build process starts, not just per-target:

1. Open your scheme editor (Product > Scheme > Edit Scheme)
2. Select the Build section on the left sidebar
3. Click the Pre-actions tab
4. Click the + button and select "New Run Script Action"
5. Under "Provide build settings from", select your main app target (so environment variables like $(SRCROOT) work as expected)
6. Paste your script command here, using the full path to your Python script
7. Ensure the Working Directory is set to $(SRCROOT) (use the folder icon to browse and select it)

This is more reliable for scripts that need to run once before any target builds kick off.

3. Leverage CocoaPods Hooks (If You Use CocoaPods) #

If your project uses CocoaPods, you can add a pre_install hook to your Podfile to trigger the script early in the build flow, before pods are processed:

pre_install do |installer|
  # Execute your Python script
  system("python3 #{Dir.pwd}/scripts/download_library.py")
end

Run pod install once after adding this, and Xcode will execute the script every time you build (since pod integration is part of the core build pipeline).

4. Switch to a Makefile as the Build Tool #

For full control over build order, you can configure Xcode to use a Makefile:

1. Create a Makefile in your project root with steps to run your script first, then build the Xcode project:

   all: download_lib build
   
   download_lib:
       python3 scripts/download_library.py
   
   build:
       xcodebuild -workspace YourApp.xcworkspace -scheme YourScheme -configuration Debug build
   

2. In Xcode, go to your target's Build Settings > Build Tool > Set to /usr/bin/make
3. Set "Build Arguments Passed to Build Tool" to all

This is a more involved setup, but it gives you complete control over the sequence of build steps.

内容的提问来源于stack exchange，提问作者ovidiu.developer