Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit bb6c179

Browse files
authoredFeb 11, 2025··
Remove CocoaPods (#23958)
* Run `pod deintegrate` and remove CocoaPods automation * Add `Makefile` automation to download Gutenberg framework * Remove dead reference to `Pods.framework` in project * Remove dead reference to pods from workspace * Remove SwiftLint-via-CocoaPods from `Rakefile` * Remove unnecessary `$(inherited)` flag from a couple of targets That's for the value `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER`, but it's useless to set `$(inherited)` for a Yes or No value because removing the value from the target will automatically make Xcode read it from the project, achieving the same result. * Remove CocoaPods instruction from the README * Remove SwiftLint instructions from the `README` * Add a version of Aztec fetched via SwiftPM * Add Gutenberg XCFrameworks via drag-n-drop from local paths * Disable `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` Was giving errors in Yoga: > Double-quoted include "YGEnums.h" in framework header, expected angle-bracketed instead * Disable `CLANG_WARN_STRICT_PROTOTYPES` It resulted in a build failure: > React.framework/Headers/RCTAppearance.h:16:60: > A function declaration without a prototype is deprecated in all versions of C * Update search path for Gutenberg React Native bundle in script * Remove some leftover bits of CocoaPods set up for automation * Remove leftover `COCOAPODS` precompiler flag Strange that `pod deintegrate` did not remove it. Maybe it was some custom piece of setup... * Remove a couple of CocoaPods-specific code branches * Temporarily switch to CI toolkit branch compatible with no CocoaPods * Fetch XCFrameworks in CI * Update Gutenberg checkout logic in localization lint for CP-less setup * Update source map upload for CP-less Gutenberg setup * Ensure `Frameworks` folder exist, otherwise tar will fail * Remove "Log Outdated Pods" step from code freeze We don't have pods anymore * Remove Pods from lists in `.gitignore` and RuboCop We don't use Pods anymore * Remove imports of Pods xcconfigs * No longer look in Pods folder to extract localizations * Link Gutenberg XCFramework in Jetpack target too! * Add instruction in README to run `make dependencies` * Use CI toolkit 3.8.0 * Point Aztec to branch in wordpress-mobile org from SPM support PR See wordpress-mobile/AztecEditor-iOS#1379 * Point Aztec to latest SwiftPM-support commit * Point to latest Aztec, 1.20.0 * Reimplement logic to download XCFrameworks from `make` to `rake` * Remove a debug `set +x` * Rewrite `gutenberg_xcframeworks` using Ruby APIs More idiomatic and safer than shelling out. See #23958 (comment) * Also delete `tar.gz` when cleaning up after setting up Gutenberg * Ignore `Pods/` for retro-compatibility
1 parent f97da7d commit bb6c179

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+179
-1224
lines changed
 

‎.buildkite/commands/build-for-testing.sh

+1-8
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,7 @@ echo "--- :beer: Installing Homebrew Dependencies"
1111
brew tap FelixHerrmann/tap
1212
brew install swift-package-list
1313

14-
echo "--- :rubygems: Setting up Gems"
15-
install_gems
16-
17-
echo "--- :cocoapods: Setting up Pods"
18-
install_cocoapods
14+
"$(dirname "${BASH_SOURCE[0]}")/shared-set-up.sh"
1915

2016
echo "--- :writing_hand: Copy Files"
2117
mkdir -pv ~/.configure/wordpress-ios/secrets
@@ -24,9 +20,6 @@ cp -v fastlane/env/project.env-example ~/.configure/wordpress-ios/secrets/projec
2420
echo "--- :closed_lock_with_key: Installing Secrets"
2521
bundle exec fastlane run configure_apply
2622

27-
echo "--- :swift: Setting up Swift Packages"
28-
install_swiftpm_dependencies
29-
3023
echo "--- :hammer_and_wrench: Building"
3124
bundle exec fastlane build_${APP}_for_testing
3225

‎.buildkite/commands/log-outdated-pods.sh

-25
This file was deleted.

0 commit comments

Comments
 (0)
Please sign in to comment.